Diagnostic and managing distributed processor system

ABSTRACT

A network of microcontrollers for monitoring and diagnosing the environmental conditions of a computer is disclosed. The network of microcontrollers provides a management system by which computer users can accurately gauge the health of their computer. The network of microcontrollers provides users the ability to detect system fan speeds, internal temperatures and voltage levels. The invention is designed to not only be resilient to faults, but also allows for the system maintenance, modification, and growth—without downtime. Additionally, the present invention allows users to replace failed components, and add new functionality, such as new network interfaces, disk interface cards and storage, without impacting existing users. One of the primary roles of the present invention is to manage the environment without outside involvement. This self-management allows the system to continue to operate even though components have failed.

RELATED APPLICATIONS

This application is a divisional of U.S. application Ser. No.11/586,282, filed on Oct. 25, 2006, which is a divisional of U.S.application Ser. No. 10/675,917, filed on Sep. 29, 2003, now U.S. Pat.No. 7,552,364, issued on Jun. 23, 2009, which is a continuation of U.S.application Ser. No. 09/911,884, filed on Jul. 23, 2001, now U.S. Pat.No. 6,681,342, issued on Jan. 20, 2004, which is a continuation of U.S.application Ser. No. 08/942,402, filed on Oct. 1, 1997, now U.S. Pat.No. 6,338,150, issued on Jan. 8, 2002, which in turn claims priority tothe following provisional patent applications, the entirety of which arehereby incorporated herein by reference:

Filing Title Appl. No. Date “Remote Access and Control of Environmental60/046,397 May 13, Management System” 1997 “Hardware and SoftwareArchitecture for Inter- 60/047,016 May 13, Connecting an EnvironmentalManagement 1997 System with a Remote Interface” “Self ManagementProtocol for a Fly-By-Wire 60/046,416 May 13, Service Processor” 1997“Computer System Hardware Infrastructure for 60/046,398 May 13, HotPlugging Single and Multi-Function PC 1997 Cards Without EmbeddedBridges” “Computer System Hardware Infrastructure for 60/046,312 May 13,Hot Plugging Multi-Function PCI Cards with 1997 Embedded Bridges”

This application is related to U.S. Pat. No. 6,249,885, entitled,“METHOD FOR MANAGING A DISTRIBUTED PROCESSOR SYSTEM”, U.S. Pat. No.6,122,758, entitled “SYSTEM FOR MAPPING ENVIRONMENTAL RESOURCES TOMEMORY FOR PROGRAM ACCESS”, and U.S. Pat. No. 6,199,173, entitled“METHOD FOR MAPPING ENVIRONMENTAL RESOURCES TO MEMORY FOR PROGRAMACCESS”, and each contains related subject matter and are eachincorporated by reference in their entirety.

APPENDICES

Appendix A, which forms a part of this disclosure, is a list of commonlyowned copending U.S. patent applications. Each one of the applicationslisted in Appendix A is hereby incorporated herein in its entirety byreference thereto.

Appendix B, which forms part of this disclosure, is a copy of the U.S.provisional patent application filed May 13, 1997, entitled “SELFMANAGEMENT PROTOCOL FOR A FLY-BY-WIRE SERVICE PROCESSOR” and assignedApplication No. 60/046,416. Page 1, line 7 of the provisionalapplication has been changed from the original to positively recite thatthe entire provisional application, including the attached documents,forms part of this disclosure.

Appendix C, which forms part of this disclosure, is a copy of the U.S.provisional patent application filed May 13, 1997, entitled “HARDWAREAND SOFTWARE ARCHITECTURE FOR INTER-CONNECTING AN ENVIRONMENTALMANAGEMENT SYSTEM WITH A REMOTE INTERFACE” and assigned Application No.60/047,016. In view of common pages between the foregoing twoapplications, a copy of only the first three pages of U.S. provisionalpatent Application No. 60/047,016 are attached hereto. Page 1, line 7 ofthe provisional application has been changed from the original topositively recite that the entire provisional application, including theattached documents, forms part of this disclosure.

COPYRIGHT RIGHTS

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention relates to the field of fault tolerant computer systems.More particularly, the invention relates to a managing and diagnosticsystem for evaluating and controlling the environmental conditions of afault tolerant computer system.

2. Description of the Related Technology

As enterprise-class servers become more powerful and more capable, theyare also becoming ever more sophisticated and complex. For manycompanies, these changes lead to concerns over server reliability andmanageability, particularly in light of the increasingly critical roleof server-based applications. While in the past many systemsadministrators were comfortable with all of the various components thatmade up a standards-based network server, today's generation of serverscan appear as an incomprehensible, unmanageable black box. Withoutvisibility into the underlying behavior of the system, the administratormust “fly blind.” Too often, the only indicators the network manager hason the relative health of a particular server is whether or not it isrunning.

It is well-acknowledged that there is a lack of reliability andavailability of most standards-based servers. Server downtime, resultingeither from hardware or software faults or from regular maintenance,continues to be a significant problem. By one estimate, the cost ofdowntime in mission critical environments has risen to an annual totalof $4.0 billion for U.S. businesses, with the average downtime eventresulting in a $140 thousand loss in the retail industry and a $450thousand loss in the securities industry. It has been reported thatcompanies lose as much as $250 thousand in employee productivity forevery 1% of computer downtime. With emerging Internet, intranet andcollaborative applications taking on more essential business roles everyday, the cost of network server downtime will continue to spiral upward.Another major cost is of system downtime administrators to diagnose andfix the system. Corporations are looking for systems which do notrequire real time service upon a system component failure.

While hardware fault tolerance is an important element of an overallhigh availability architecture, it is only one piece of the puzzle.Studies show that a significant percentage of network server downtime iscaused by transient faults in the I/O subsystem. Transient failures arethose which make a server unusable, but which disappear when the serveris restarted, leaving no information which points to a failingcomponent. These faults may be due, for example, to the device driver,the adapter card firmware, or hardware which does not properly handleconcurrent errors, and often causes servers to crash or hang. The resultis hours of downtime per failure, while a system administrator discoversthe failure, takes some action and manually reboots the server. In manycases, data volumes on hard disk drives become corrupt and must berepaired when the volume is mounted. A dismount-and-mount cycle mayresult from the lack of hot pluggability in current standards-basedservers. Diagnosing intermittent errors can be a frustrating andtime-consuming process. For a system to deliver consistently highavailability, it should be resilient to these types of faults.

Modern fault tolerant systems have the functionality monitor the ambienttemperature of a storage device enclosure and the operational status ofother components such the cooling fans and power supply. However, alimitation of these server systems is that they do not containself-managing processes to correct malfunctions. Thus, if a malfunctionoccurs in a typical server, the one corrective measure taken by theserver is to give notification of the error causing event via a computermonitor to the system administrator. If the system error caused thesystem to stop running, the system administrator might never know thesource of the error. Traditional systems are lacking in detail andsophistication when notifying system administrators of systemmalfunctions. System administrators are in need of a graphical userinterface for monitoring the health of a network of servers.Administrators need a simple point-and-click interface to evaluate thehealth of each server in the network. In addition, existing faulttolerant servers rely upon operating system maintained logs for errorrecording. These systems are not capable of maintaining information whenthe operating system is inoperable due to a system malfunction.

Existing systems also do not have an interface to control the changingor addition of an adapter. Since any user on a network could be using aparticular device on the server, system administrators need a softwareapplication that will control the flow of communications to a devicebefore, during, and after a hot plug operation on an adapter.

Also, in the typical fault tolerant computer system, the control logicfor the diagnostic system is associated with a particular processor.Thus, if the environmental control processor malfunctioned, then alldiagnostic activity on the computer would cease. In traditional systems,there is no monitoring of fans, and no means to make up cooling capacitylost when a fan fails. Some systems provide a processor located on aplug-in PCI card which can monitor some internal systems, and controlturning power on and off. If this card fails, obtaining informationabout the system, and controlling it remotely, is no longer possible.Further, these systems are not able to affect fan speed or coolingcapacity.

Therefore, a need exists for improvements in server management whichwill result in greater reliability and dependability of operation.Server users are in need of a management system by which the users canaccurately gauge the health of their system. Users need a highavailability system that should not only be resilient to faults, butshould allow for maintenance, modification, and growth—without downtime.System users should be able to replace failed components, and add newfunctionality, such as new network interfaces, disk interface cards andstorage, without impacting existing users. As system demands grow,organizations must frequently expand, or scale, their computinginfrastructure, adding new processing power, memory, storage and I/Ocapacity. With demand for 24-hour access to critical, server-basedinformation resources, planned system downtime for system service orexpansion has become unacceptable.

SUMMARY OF THE INVENTION

Embodiments of the inventive monitoring and management system providesystem administrators with new levels of client/server systemavailability and management. It gives system administrators and networkmanagers a comprehensive view into the underlying health of theserver—in real time, whether on-site or off-site. In the event of afailure, the invention enables the administrator to learn why the systemfailed, why the system was unable to boot, and to control certainfunctions of the server.

One embodiment of the invention is a computer monitoring and diagnosticsystem, comprising: a computer; a plurality of sensors capable ofsensing conditions of the computer; and a microcontroller network,comprising a plurality of interconnected microcontrollers, connected tothe sensors and the computer, wherein the microcontroller networkprocesses requests for conditions from the computer and responsivelyprovides sensed conditions to the computer.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is one embodiment of a top-level block diagram showing a faulttolerant computer system of the invention, including mass storage andnetwork connections.

FIG. 2 is one embodiment of a block diagram showing a first embodimentof a multiple bus configuration connecting I/O adapters and a network ofmicrocontrollers to the clustered CPUs of the fault tolerant computersystem shown in FIG. 1.

FIG. 3 is one embodiment of a block diagram showing a second embodimentof a multiple bus configuration connecting canisters containing I/Oadapters and a network of microcontrollers to the clustered CPUs of thefault tolerant system shown in FIG. 1.

FIG. 4 is one embodiment of a top-level block diagram illustrating themicrocontroller network shown in FIGS. 2 and 3.

FIGS. 5A, 5B, and 5C are detailed block diagrams showing one embodimentof the microcontroller network shown in FIG. 4 illustrating the signalsand values monitored by each microcontroller, and the control signalsgenerated by the microcontrollers.

FIG. 6 is one embodiment of a flowchart showing the process by which aremote user can access diagnostic and managing services of themicrocontroller network shown in FIGS. 5A, 5B, and 5C.

FIG. 7 is one embodiment of a block diagram showing the connection of anindustry standard architecture (ISA) bus to the microcontroller networkshown in FIGS. 4, 5A, 5B, and 5C.

FIG. 8 is one embodiment of a flowchart showing the master to slavecommunications of the microcontrollers shown in FIGS. 4, 5A, 5B, and 5C.

FIG. 9 is one embodiment of a flowchart showing the slave to mastercommunications of the microcontrollers shown in FIGS. 4, 5A, 5B, and 5C.

FIGS. 10A and 10B are flowcharts showing one process by which the SystemInterface, shown in FIGS. 4, 5A, 5B, and 5C, gets commands and relayscommands from the ISA bus to the network of microcontrollers.

FIGS. 11A and 11B are flowcharts showing one process by which a Chassismicrocontroller, shown in FIGS. 4, 5A, 5B, and 5C, manages and diagnosesthe power supply to the computer system.

FIG. 12 is a flowchart showing one process by which the Chassiscontroller, shown in FIGS. 4, 5A, 5B, and 5C, monitors the addition andremoval of a power supply from the fault tolerant computer system.

FIG. 13 is a flowchart showing one process by which the Chassiscontroller, shown in FIGS. 4, 5A, 5B, and 5C, monitors temperature.

FIGS. 14A and 14B are flowcharts showing one embodiment of theactivities undertaken by CPU A controller, shown in FIGS. 4, 5A, 5B, and5C.

FIG. 15 is a detailed flowchart showing one process by which the CPU Acontroller, show in FIGS. 4, 5A, 5B, and 5C, monitors the fan speed forthe system board of the computer.

FIG. 16 is a flowchart showing one process by which activities of theCPU B controller, shown in FIGS. 4, 5A, 5B, and 5C, scans for systemfaults.

FIG. 17 is a flowchart showing one process by which activities of aCanister controller, shown in FIGS. 4, 5A, 5B, and 5C, monitors thespeed of the canister fan of the fault tolerant computer system.

FIG. 18 is a flowchart showing one process by which activities of theSystem Recorder, shown in FIGS. 4, 5A, 5B, and 5C, resets the NVRAMlocated on the backplane of the fault tolerant computer system.

DETAILED DESCRIPTION OF THE INVENTION

The following detailed description presents a description of certainspecific embodiments of the invention. However, the invention can beembodied in a multitude of different ways as defined and covered by theclaims. In this description, reference is made to the drawings whereinlike parts are designated with like numerals throughout.

FIG. 1 is one embodiment of a block diagram showing a fault tolerantcomputer system of the invention. Typically the computer system is oneserver in a network of servers and communicating with client computers.Such a configuration of computers is often referred to as aclient-server architecture. A fault tolerant server is useful formission critical applications such as the securities business where anycomputer down time can result in catastrophic financial consequences. Afault tolerant computer will allow for a fault to be isolated and notpropagate through the system thus providing complete or minimaldisruption to continuing operation. Fault tolerant systems also provideredundant components such as adapters so service can continue even whenone component fails.

The system includes a fault tolerant computer system 100 connecting toexternal peripheral devices through high speed I/O channels 102 and 104.The peripheral devices communicate and are connected to the high speedI/O channels 102 and 104 by mass storage buses 106 and 107. In differentembodiments of the invention, the bus system 106, 107 could bePeripheral Component Interconnect (PCI), Microchannel, IndustrialStandard Architecture (ISA) and Extended ISA (EISA) architectures. Inone embodiment of the invention, the buses 106, 107 are PCI. Variouskinds of peripheral controllers 108, 112, 116, and 128, may be connectedto the buses 106 and 107 including mass storage controllers, networkadapters and communications adapters. Mass storage controllers attach todata storage devices such as magnetic disk, tape, optical disk, CD-ROM.These data storage devices connect to the mass storage controllers usingone of a number of industry standard interconnects, such as smallcomputer storage interface (SCSI), IDE, EIDE, SMD. Peripheralcontrollers and I/O devices are generally off-the-shelf products. Forinstance, sample vendors for a magnetic disk controller 108 and magneticdisks 110 include Qlogic, and Quantum (respectively). Each magnetic diskmay hold multiple Gigabytes of data.

A client server computer system typically includes one or more networkinterface controllers (NICs) 112 and 128. The network interfacecontrollers 112 and 128 allow digital communication between the faulttolerant computer system 100 and other computers (not shown) such as anetwork of servers via a connection 130. For LAN embodiments of thenetwork adapter, the network media used may be, for example, Ethernet(IEEE 802.3), Token Ring (IEEE 802.5), Fiber Distributed DatalinkInterface (FDDI) or Asynchronous Transfer Mode (ATM).

In the computer system 100, the high speed I/O channels, buses andcontrollers (102-128) may, for instance, be provided in pairs. In thisexample, if one of these should fail, another independent channel, busor controller is available for use until the failed one is repaired.

In one embodiment of the invention, a remote computer 130 is connectedto the fault tolerant computer system 100. The remote computer 130provides some control over the fault tolerant computer system 100, suchas requesting system status.

FIG. 2 shows one embodiment of the bus structure of the fault tolerantcomputer system 100. A number ‘n’ of central processing units (CPUs) 200are connected through a host bus 202 to a memory controller 204, whichallows for access to semiconductor memory by the other systemcomponents. In one embodiment of the invention, there are four CPUs 200,each being an Intel Pentium® Pro microprocessor. A number of bridges206, 208 and 209 connect the host bus to three additional bus systems212, 214, and 216. These bridges correspond to high speed I/O channels102 and 104 shown in FIG. 1. The buses 212, 214 and 216 correspond tothe buses 106 and 107 shown in FIG. 1. The bus systems 212, 214 and 216,referred to as PC buses, may be any standards-based bus system such asPCI, ISA, EISA and Microchannel. In one embodiment of the invention, thebus systems 212, 214, 216 are PCI. In another embodiment of theinvention a proprietary bus is used.

An ISA Bridge 218 is connected to the bus system 212 to support legacydevices such as a keyboard, one or more floppy disk drives and a mouse.A network of microcontrollers 225 is also interfaced to the ISA bus 226to monitor and diagnose the environmental health of the fault tolerantsystem. Further discussion of the network will be provided below.

A bridge 230 and a bridge 232 connects PC buses 214 and 216 with PCbuses 234 and 236 to provide expansion slots for peripheral devices oradapters. Separating the devices 238 and 240 on PC buses 234 and 236reduces the potential that a device or other transient I/O error willbring the entire system down or stop the system administrator fromcommunicating with the system.

FIG. 3 shows an alternative bus structure embodiment of the faulttolerant computer system 100. The two PC buses 214 and 216 containbridges 242, 244, 246 and 248 to PC bus systems 250, 252, 254, and 256.As with the PC buses 214 and 216, the PC buses 250, 252, 254 and 256 canbe designed according to any type of bus architecture including PCI,ISA, EISA, and Microchannel. The PC buses 250, 252, 254, and 256 areconnected, respectively, to a canister 258, 260, 262 and 264. Thecanisters 258, 260, 262, and 264 are casings for a detachable bus systemand provide multiple slots for adapters. In the illustrated canister,there are four adapter slots.

Referring now to FIG. 4, the present invention for monitoring anddiagnosing environmental conditions may be implemented by using anetwork of microcontrollers 225 located on the fault tolerant computersystem 100. In one embodiment some of the microcontrollers are placed ona system board or motherboard 302 while other microcontrollers areplaced on a backplane 304. Furthermore, in the embodiment of FIG. 3,some of the microcontrollers such as Canister controller A 324 mayreside on a removable canister.

FIG. 4 illustrates that the network of microcontrollers 225 is connectedto one of the CPUs 200 by an ISA bus 308. The ISA 308 bus interfaces thenetwork of microcontrollers 225 which are connected on themicrocontroller bus 310 through a System Interface 312. In oneembodiment of the invention, the microcontrollers communicate through anI²C serial bus, also referred to as a microcontroller bus 310. Thedocument “The I²C Bus and How to Use It” (Philips Semiconductor, 1992)is hereby incorporated by reference. The I²C bus is a bi-directionaltwo-wire bus and operates at a 400 kbps rate in the present embodiment.However, other bus structures and protocols could be employed inconnection with this invention. In other embodiments, IEEE 1394(Firewire), IEEE 422, IEEE 488 (GPIB), RS-185, Apple ADB, UniversalSerial Bus (USB), or Controller Area Network (CAN) could be utilized asthe microcontroller bus. Control on the microcontroller bus isdistributed. Each microcontroller can be a sender (a master) or areceiver (a slave) and each is interconnected by this bus. Amicrocontroller directly controls its own resources, and indirectlycontrols resources of other microcontrollers on the bus.

Here are some of the features of the I²C-bus:

-   -   Only two bus line are required: a serial data line (SDA) and a        serial clock line (SCL).    -   Each device connected to the bus is software addressable by a        unique address and simple master/slave relationships exist at        all times; masters can operate as master-transmitters or as        master-receivers.    -   The bus is a true multi-master bus including collision detection        and arbitration to prevent data corruption if two or more        masters simultaneously initiate data transfer.    -   Serial, 8-bit oriented, bi-directional data transfers can be        made at up to 400 Kbit/second in the fast mode.

Two wires, serial data (SDA) and serial clock (SCL), carry informationbetween the devices connected to the I²C bus. Each device is recognizedby a unique address and can operate as either a transmitter or receiver,depending on the function of the device. Further, each device canoperate from time to time as both a transmitter and a receiver. Forexample, a memory device connected to the I²C bus could both receive andtransmit data. In addition to transmitters and receivers, devices canalso be considered as masters or slaves when performing data transfers(see Table 1). A master is the device which initiates a data transfer onthe bus and generates the clock signals to permit that transfer. At thattime, any device addressed is considered a slave.

TABLE 1 Definition of I²C-bus terminology Term Description TransmitterThe device which sends the data to the bus Receiver The device whichreceives the data from the bus Master The device which initiates atransfer, generates clock signals and terminates a transfer Slave Thedevice addressed by a master Multi-master More than one master canattempt to control the bus at the same time without corrupting themessage. Each device at separate times may act as a master. ArbitrationProcedure to ensure that, if more than one master simultaneously triesto control the bus, only one is allowed to do so and the message is notcorrupted Synchronization Procedure to synchronize the clock signal oftwo or more devices

The I²C-bus is a multi-master bus. This means that more than one devicecapable of controlling the bus can be connected to it. As masters areusually microcontrollers, consider the case of a data transfer betweentwo microcontrollers connected to the I²C-bus. This highlights themaster-slave and receiver-transmitter relationships to be found on theI²C-bus. It should be noted that these relationships are not permanent,but only depend on the direction of data transfer at that time. Thetransfer of data between microcontrollers is further described in FIG.8.

The possibility of connecting more than one microcontroller to theI²C-bus means that more than one master could try to initiate a datatransfer at the same time. To avoid the conflict that might ensue fromsuch an event, an arbitration procedure has been developed. Thisprocedure relies on the wired-AND connection of all I²C interfaces tothe I²C-bus.

If two or more masters try to put information onto the bus, as long asthey put the same information onto the bus, there is no problem. Eachmonitors the state of the SDL. If a microcontroller expects to find thatthe SDL is high, but finds that it is low, the microcontroller assumesit lost the arbitration and stops sending data. The clock signals duringarbitration are a synchronized combination of the clocks generated bythe masters using the wired-AND connection to the SCL line.

Generation of clock signal on the I²C-bus is always the responsibilityof master devices. Each master microcontroller generates its own clocksignals when transferring data on the bus.

In one embodiment, the command, diagnostic, monitoring and historyfunctions of the microcontroller network 102 are accessed using a globalnetwork memory and a protocol has been defined so that applications canaccess system resources without intimate knowledge of the underlyingnetwork of microcontrollers. That is, any function may be queried simplyby generating a network “read” request targeted at the function's knownglobal network address. In the same fashion, a function may be exercisedsimply by “writing” to its global network address. Any microcontrollermay initiate read/write activity by sending a message on the I²C bus tothe microcontroller responsible for the function (which can bedetermined from the known global address of the function). The networkmemory model includes typing information as part of the memoryaddressing information.

Referring to FIG. 4, in one embodiment of the invention, the network ofmicrocontrollers 310 includes ten processors. One of the purposes of themicrocontroller network 225 is to transfer messages to the othercomponents of the server system 100. The processors or microcontrollersinclude: a System Interface 312, a CPU A controller 314, a CPU Bcontroller 316, a System Recorder 320, a Chassis controller 318, aCanister A controller 324, a Canister B controller 326, a Canister Ccontroller 328, a Canister D controller 330 and a Remote Interfacecontroller 332. The System Interface controller 312, the CPU Acontroller 314 and the CPU B controller 316 are located on a systemboard 302 in the fault tolerant computer system 100. Also located on thesystem board are one or more central processing units (CPUs) ormicroprocessors 164 and the Industry Standard Architecture (ISA) bus 296that connects to the System Interface Controller 312. The CPUs 200 maybe any conventional general purpose single-chip or multi-chipmicroprocessor such as a Pentium7, Pentium® Pro or Pentium® II processoravailable from Intel Corporation, A MIPS® processor available fromSilicon Graphics, Inc., a SPARC processor from Sun Microsystems, Inc., aPower PC® processor available from Motorola, or an ALPHA® processoravailable from Digital Equipment Corporation. In addition, the CPUs 200may be any conventional special purpose microprocessor such as a digitalsignal processor or a graphics processor.

The System Recorder 320 and Chassis controller 318, along with a datastring such as a random access non-volatile access memory (NVRAM) 322that connects to the System Recorder 320, are located on a backplane 304of the fault tolerant computer system 100. The data storage 322 may beindependently powered and may retain its contents when power isunavailable. The data storage 322 is used to log system status, so thatwhen a failure of the computer 100 occurs, maintenance personnel canaccess the storage 322 and search for information about what componentfailed. An NVRAM is used for the data storage 322 in one embodiment butother embodiments may use other types and sizes of storage devices.

The System Recorder 320 and Chassis controller 318 are the firstmicrocontrollers to power up when server power is applied. The SystemRecorder 320, the Chassis controller 318 and the Remote Interfacemicrocontroller 332 are the three microcontrollers that have anindependent bias 5 Volt power supplied to them if main server power isoff. This independent bias 5 Volt power is provided by a RemoteInterface Board (not shown). The Canister controllers 324-330 are notconsidered to be part of the backplane 304 because each is mounted on acard attached to the canister.

FIGS. 5A, 5B, and 5C are one embodiment of a block diagram thatillustrates some of the signal lines that are used by the differentmicrocontrollers. Some of the signal lines connect to actuators andother signal lines connect to sensors. In one embodiment of theinvention the microcontrollers in the network are commercially availablemicrocontrollers. Examples of off-the-shelf microcontrollers are thePIC16c65 and the PIC16c74 available from Microchip Technology Inc, the8051 from Intel Corporation, the 8751 available from Atmel, and aP80CL580 microprocessor available from Philips, could be utilized.

The Chassis controller 318 is connected to a set of temperaturedetectors 502, 504, and 506 which read the temperature on the backplane304 and the system board 302. FIG. 5 also illustrates the signal linesthat connect the System Recorder 320 to the NVRAM 322 and a timer chip520. In one embodiment of the invention, the System Recorder 320 is theonly microcontroller that can access the NVRAM 322. The Canistercontroller 324 is connected to a Fan Tachometer Signal Mux 508 which isused to detect the speed of the fans. The CPU A controller 314 also isconnected to a fan mux 508 which gathers the fan speed of system fans.The CPU A controller 314 displays errors to a user by writing to an LCDdisplay 512. Any microcontroller can request the CPU A controller 314 towrite a message to the LCD display 512. The System Interface 312 isconnected to a response buffer 514 which queues outgoing responsesignals in the order that they are received. Similarly, a request signalbuffer 516 is connected to the System Interface 312 and stores, orqueues request signals in the order that they are received.

Software applications can access the network of microcontrollers 225 byusing the software program header file that is listed at the end of thespecification in the section titled “Header File for Global MemoryAddresses”. This header file provides a global memory address for eachfunction of the microcontroller network 225. By using the definitionsprovided by this header file, applications can request and sendinformation to the microcontroller network 225 without needing to knowwhere a particular sensor or activator resides in the microcontrollernetwork.

FIG. 6 is one embodiment of a flowchart illustrating the process bywhich under one implementation of the present invention, a remoteapplication connected, say, through the connection of FIG. 1, can accessthe network of microcontrollers 225. Starting at state 600, a remotesoftware application, such as a generic system management applicationlike Hewlett-Packard Open View, or an application specific to thiscomputer system, retrieves a management information block (MIB) objectby reading and interpreting a MIB file, or by an application's implicitknowledge of the MIB object's structure. This retrieval could be theresult of an operator using a graphical user interface (GUI), or as theresult of some automatic system management process. The MIB is adescription of objects, which have a standard structure, and containinformation specific to the MIB object ID associated with a particularMIB object. At a block 602, the remote application builds a request forinformation by creating a request which references a particular MIBobject by its object ID, sends the request to the target computer usinga protocol called SNMP (simple network management protocol). SNMP is atype of TCP/IP protocol. Moving to state 604, the remote software sendsthe SNMP packet to a local agent Microsoft WinSNMP, for example, whichis running on the fault tolerant computer system 100, which includes thenetwork of microcontrollers 225 (FIG. 4). The agent is a specializedprogram which can interpret MIB object Ids and objects. The local agentsoftware runs on one of the CPUs 200 of FIGS. 2 and 3.

The local agent examines the SNMP request packet (state 606). If thelocal agent does not recognize the request, the local agent passes theSNMP packet to an extension SNMP agent. Proceeding to state 608, theextension SNMP agent dissects the object ID. The extension SNMP agent iscoded to recognize from the object ID, which memory mapped resourcesmanaged by the network of microcontrollers need to be accessed (state608). The agent then builds the required requests for the memory mappedinformation in the command protocol format understood by the network ofmicrocontrollers 225. The agent then forwards the request to amicrocontroller network device driver (state 610).

The device driver then sends the information to the network ofmicrocontrollers 225 at state 612. The network of microcontrollers 225provides a result to the device driver in state 614. The result isreturned to the extension agent, which uses the information to build theMIB object, and return it to the extension SNMP agent (state 616). Thelocal SNMP agent forwards the MIB object via SNMP to the remote agent(state 616). Finally, in state 620, the remote agent forwards the resultto the remote application software.

For example, if a remote application needs to know the speed of a fan,the remote application reads a file to find the object ID for fan speed.The object ID for the fan speed request may be “837.2.3.6.2”. Each setof numbers in the object ID represent hierarchical groups of data. Forexample the number “3” of the object ID represents the cooling system.The “3.6” portion of the object ID represents the fans in the cooling.All three numbers “3.6.2” indicate speed for a particular fan in aparticular cooling group.

In this example, the remote application creates a SNMP packet containingthe object ID to get the fan speed on the computer 100. The remoteapplication then sends the SNMP packet to the local agent. Since thelocal agent does not recognize the fan speed object ID, the local agentforwards the SNMP packet to the extension agent. The extension agentparses the object ID to identify which specific memory mapped resourcesof the network of microcontrollers 225 are needed to build the MIBobject whose object ID was just parsed. The extension agent then createsa message in the command protocol required by the network ofmicrocontrollers 225. A device driver which knows how to communicaterequests to the network of microcontrollers 225 takes this message andrelays the command to the network of microcontrollers 225. Once thenetwork of microcontrollers 225 finds the fan speed, it relays theresults to the device driver. The device driver passes the informationto the extension agent. The agent takes the information supplied by themicrocontroller network device driver and creates a new SNMP packet. Thelocal agent forwards this packet to the remote agent, which then relaysthe fan speed which is contained in the packet to the remote applicationprogram.

FIG. 7 is one embodiment of a block diagram of the interface between thenetwork of microcontrollers 225 and the ISA bus 308 of FIGS. 2 and 3.The interface to the network of microcontrollers 225 includes a SystemInterface processor 312 which receives event and request signals,processes these signals, and transmits command, status and responsesignals to the operating system of the CPUs 200. In one embodiment, theSystem Interface processor 312 is a PIC16C65 controller chip, availablefrom Microchip, Technology Inc., which includes an event memory (notshown) organized as a bit vector, having at least sixteen bits. Each bitin the bit vector represents a particular type of event. Writing anevent to the System Interface processor 312 sets a bit in the bit vectorthat represents the event. Upon receiving an event signal from anothermicrocontroller, the System Interface 312 interrupts CPUs 200. Uponreceiving the interrupt, the CPUs 200 will check the status of theSystem Interface 312 to ascertain that an event is pending.Alternatively, the CPUs 200 may periodically poll the status of theSystem Interface 312 to ascertain whether an event is pending. The CPUs200 may then read the bit vector in the System Interface 312 toascertain the type of event that occurred and thereafter notify a systemoperator of the event by displaying an event message on a monitorconnected to the fault tolerant computer 100 or another computer in theserver network. After the system operator has been notified of theevent, as described above, she may then obtain further information aboutthe system failure which generated the event signal by accessing theNVRAM 322.

The System Interface 312 communicates with the CPUs 200 by receivingrequest signals from the CPUs 200 and sending response signals back tothe CPUs 200. Furthermore, the System Interface 312 can send and receivestatus and command signals to and from the CPUs 200. For example, arequest signal may be sent from a software application inquiring as towhether the System Interface 312 has received any event signals, orinquiring as to the status of a particular processor, subsystem,operating parameter. The following discussion explains how in furtherdetail at the state 612, the device driver sends the request to thenetwork on microcontrollers, and then, how the network onmicrocontrollers returns the result (state 614). A request signal buffer516 is connected to the System Interface 312 and stores, or queues,request signals in the order that they are received, first in-first out(FIFO). Similarly, a response buffer 514 is connected to the SystemInterface 312 and queues outgoing response signals in the order thatthey are received (FIFO). These queues are one byte wide, (messages onthe I²C bus are sequences of 8-bit bytes, transmitted bit serially onthe SDL).

A message data register (MDR) 707 is connected to the request andresponse buffers 516 and 514 and controls the arbitration of messages toand from the System Interface 312 via the request and response buffers516 and 514. In one embodiment, the MDR 707 is eight bits wide and has afixed address which may be accessed by the server's operating system viathe ISA bus 226 connected to the MDR 707. As shown in FIG. 7, the MDR707 has an I/O address of 0CC0h. When software application running onone of the CPUs 200 desires to send a request signal to the SystemInterface 312, it does so by writing a message one byte at a time to theMDR 707. The application then indicates to the system interfaceprocessor 312 that the command has been completely written, and may beprocessed.

The system interface processor 312 writes the response one byte at atime to the response queue, then indicates to the CPU (via an interruptor a bit in the status register) that the response is complete, andready to be read. The CPU 200 then reads the response queue one byte ata time by reading the MDR 707 until all bytes of the response are read.

The following is one embodiment of the command protocol used tocommunicate with the network of microcontrollers 225.

TABLE 2 Command Protocol Format READ REQUEST FORMAT WRITE REQUEST FORMATOffset Offset Byte 0 Slave Addr 0 Byte 0 Slave Addr 0 (7 bits) LSBit (7bits) LSBit Byte 1 MSBit (1) Type Byte 1 MSBit (0) Type Byte 2 CommandID (LSB) Byte 2 Command ID (LSB) Byte 3 Command ID (MSB) Byte 3 CommandID (MSB) Byte 4 Read Request Length (N) Byte 4 Write Request Length (N)Byte 5 Check Sum Byte 5 Data Byte 1 . . . . . . Byte N + 4 Data Byte NByte N + 5 Check Sum READ RESPONSE FORMAT WRITE RESPONSE FORMAT OffsetOffset Byte 0 Slave Add 1 Byte 0 Slave Addr 1 (7 bits) LSBit (7 bits)LSBit Byte 1 Read Response Length Byte 1 Write (N) Response Length (0)Byte 2 Data Byte 1 Byte 2 Status . . Byte 3 Check Sum . . Byte 4Inverted Slave Addr . . Byte N + Data Byte N 1 Byte N + Status 2 ByteN + Check Sum 3 Byte N + Inverted Slave Addr 4

The following is a description of each of the fields in the commandprotocol.

TABLE 3 Description of Command Protocol Fields FIELD DESCRIPTION SlaveAddr Specifies the processor identification code. This field is 7 bitswide. Bit[7 . . . 1]. LSBit Specifies what type of activity is takingplace. If LSBit is clear (0), the master is writing to a slave. If LSBitis set (1), the master is reading from a slave. MSBit Specifies the typeof command. It is bit 7 of byte 1 of a request. If this bit is clear(0), this is a write command. If it is set (1), this is a read command.Type Specifies the data type of this command, such as bit or string.Command ID (LSB) Specifies the least significant byte of the address ofthe processor. Command ID (MSB) Specifies the most significant byte ofthe address of the processor. Length (N) Read Request Specifies thelength of the data that the master expects to get back from a readresponse. The length, which is in bytes, does not include the Status,Check Sum, and Inverted Slave Addr fields. Read Response Specifies thelength of the data immediately following this byte, that is byte 2through byte N + 1. The length, which is in bytes, does not include theStatus, Check Sum, and Inverted Slave Addr fields. Write RequestSpecifies the length of the data immediately following this byte, thatis byte 2 through byte N + 1. The length, which is in bytes, does notinclude the Status, Check Sum, and Inverted Slave Addr fields. WriteResponse Always specified as 0. Data Byte 1 Specifies the data in a readrequest and response, and a write request. Data Byte N Status Specifieswhether or not this command executes successfully. A non-zero entryindicates a failure. Check Sum Specifies a direction control byte toensure the integrity of a message on the wire. Inverted Slave AddrSpecifies the Slave Addr, which is inverted.

The System Interface 312 further includes a command and status register(CSR) 709 which initiates operations and reports on status. Theoperation and functionality of CSR 709 is described in further detailbelow. Both synchronous and asynchronous I/O modes are provided by theSystem Interface 312. During a synchronous mode of operation, the devicedriver waits for a request to be completed. During an asynchronous modeof operation the device driver sends the request, and asks to beinterrupted when the request completes. To support asynchronousoperations, an interrupt line 711 is connected between the SystemInterface 312 and the ISA bus 226 and provides the ability to request aninterrupt when asynchronous I/O is complete, or when an event occurswhile the interrupt is enabled. As shown in FIG. 7, in one embodiment,the address of the interrupt line 711 is fixed and indicated as IRQ 15which is an interrupt address number used specifically for the ISA bus226.

The MDR 707 and the request and response buffers 516 and 514,respectively, transfer messages between a software application runningon the CPUs 200 and the failure reporting system of the invention. Thebuffers 516 and 514 have two functions: (1) they store data insituations where one bus is running faster than the other, i.e., thedifferent clock rates, between the ISA bus 226 and the microcontrollerbus 310; and (2) they serve as interim buffers for the transfer ofmessages—this relieves the System Interface 312 of having to providethis buffer.

When the MDR 707 is written to by the ISA bus 226, it loads a byte intothe request buffer 516. When the MDR 707 is read from the ISA bus 516,it unloads a byte from the response buffer 514. The System Interface 312reads and executes messages from buffer 516 when a message command isreceived in the CSR 709. A response message is written to the responsebuffer 514 when the System Interface 312 completes executing thecommand. The system operator receives a completed message over themicrocontroller bus 310. A software application can read and writemessage data to and from the buffers 516 and 514 by executing read andwrite instructions through the MDR 707.

The CSR 709 has two functions. The first is to initiate commands, andthe second is to report status. The System Interface commands areusually executed synchronously. That is, after issuing a command, themicrocontroller network device driver should continue to poll the CSR709 status to confirm command completion. In addition to synchronous I/Omode, the microcontroller network device driver can also request anasynchronous I/O mode for each command by setting a “Asyn Req” bit inthe command. In this mode, an interrupt is generated and sent to the ISAbus 226, via the interrupt line 711, after the command has completedexecuting.

In the described embodiment, the interrupt is asserted through IRQ15 ofthe ISA programmable interrupt controller (PIC). The ISA PIC interruptsthe CPU 200 s when a signal transitioning from high to low, or from lowto high, is detected at the proper input pin (edge triggered).Alternatively, the interrupt line 711 may utilize connect to alevel-triggered input. A level-triggered interrupt request is recognizedby keeping the signal at the same level, or changing the level of asignal, to send an interrupt. The microcontroller network device drivercan either enable or disable interrupts by sending “Enable Ints” and“Disable Ints” commands to the CSR 701. If the interrupt 711 line isenabled, the System Interface 312 asserts the interrupt signal IRQ15 ofthe PIC to the ISA bus 226, either when an asynchronous I/O is completeor when an event has been detected.

In the embodiment shown in FIG. 2, the System Interface 312 may be asingle-threaded interface. Since messages are first stored in the queue,then retrieved from the queue by the other side of the interface, adevice driver should write one message, containing a sequence of bytes,at a time. Thus, only one message should be in progress at a time usingthe System Interface 312. Therefore, a program or application mustallocate the System Interface 312 for its use before using it, and thende-allocate the interface 514 when its operation is complete. The CSR709 indicates which operator is allocated access to the System Interface312.

Referring to FIGS. 2 and 7, an example of how messages are communicatedbetween the System Interface 312 and CPUs 200 in one embodiment of theinvention is as follows (all byte values are provided in hexadecimalnumbering). A system management program (not shown) sends a command tothe network of microcontrollers 225 to check temperature and fan speed.To read the temperature from CPU A controller 314 the program builds amessage for the device driver to forward to the network ofmicrocontrollers 225. First, the device driver on CPUs 200 allocates theinterface by writing the byte “01” to the CSR 709. If another requestwas received, the requestor would have to wait until the previousrequest was completed. To read the temperature from Chassis controller318 the device driver would write into the request queue 516 through theMDR 707 the bytes “02 83 03 00 FF”. The first byte “02” would signify tothe System Interface 312 that a command is intended for the Chassiscontroller 318. The first bits of the second byte “83” indicates that amaster is writing to a slave. The last or least significant three bitsof the byte “83” indicate the data type of the request. The third andfourth bytes “03 00” indicate that the read request temperature functionof the Chassis controller 318 is being requested. The final byte “FF” isthe checksum.

After writing the bytes to the MDR 707, a “13” (message command) iswritten by the device driver to the CSR 709, indicating the command isready to be executed. The System Interface processor 312 passes themessage bytes to the microcontroller bus 310, receives a response, andputs the bytes into the response FIFO 514. Since there is only onesystem interface processor 312, there is no chance that message byteswill get intermingled.

After all bytes are written to the response FIFO, the System Interfaceprocessor 312 sets a bit in the CSR 709 indicating message completion.If directed to do so by the device driver, the system interface 312asserts an interrupt on IRQ 15 upon completion of the task.

The CPUs 200 would then read from the response buffer 516 through theMDR 707 the bytes “02 05 27 3C 27 26 27 00”. The first byte in thestring is the slave address shown as Byte 0 in the Read Response Format.The first byte 02 indicates that the CPU A Chassis controller 318 wasthe originator of the message. The second byte “05” indicates the numberof temperature readings that follow. The second Byte “05” maps to Byte 1of the Read Response Format. In this example, the Chassis controller 318returned five temperatures. The second reading, byte “3C” (60 decimal)is above normal operational values. The last byte “00” is a check sumwhich is used to ensure the integrity of a message.

The CPUs 200 agent and device driver requests the fan speed by writingthe bytes “03 83 04 00 FF” to the network of microcontroller 225. Eachbyte follows the read request format specified in Table 2. The firstbyte “03” indicates that the command is for the CPU A Controller 314.The second byte “83” indicates that the command is a read request of astring data type.

A response of “03 06 41 43 41 42 41 40 00” would be read from MDR 707 bythe device driver. The first byte “03” indicates to the device driverthat the command is from the CPU A controller 314. The speed bytes “4143 41 42 41 40” indicate the revolutions per second of a fan inhexadecimal. The last byte read from the MDR 707 “00” is the checksum.

Since one of the temperatures is higher than the warning threshold, 55°C., and fan speed is within normal (low) range, a system administratoror system management software may set the fan speed to high with thecommand bytes “03 01 01 00 01 01 FF”. The command byte “03” indicatesthat the command is for the CPU A 314. The first byte indicates that awrite command is requested. The third and fourth bytes, which correspondto byte 2 and 3 of the write request format, indicate a request toincrease the fan speed. The fifth byte, which corresponds to byte 4 ofthe write request format indicates to the System Interface 312 that onebyte is being sent. The sixth byte contains the data that is being sent.The last byte “FF” is the checksum.

FIG. 8 is one embodiment of a flowchart describing the process by whicha master microcontroller communicates with a slave microcontroller.Messages between microcontrollers can be initiated by anymicrocontroller on the microcontroller bus 310 (FIG. 4). A mastermicrocontroller starts out in state 800.

In state 802, the microcontroller arbitrates for the start bit. If amicrocontroller sees a start bit on the microcontroller bus 310, itcannot gain control of the microcontroller bus 310. The mastermicrocontroller proceeds to state 804. In the state 804, themicrocontroller increments a counter every millisecond. Themicrocontroller then returns to state 800 to arbitrate again for thestart bit. If at state 806 the count reaches 50 ms, the master hasfailed to gain the bus (states 808 and 810). The microcontroller thenreturns to the state 800 to retry the arbitration process.

If in the state 802, no start bit is seen on the microcontroller bus310, the microcontroller bus 310 is assumed to be free (i.e., themicrocontroller has successfully arbitrated won arbitration for themicrocontroller bus 310). The microcontroller sends a byte at a time onthe microcontroller bus 310 (state 812). After the microcontroller hassent each byte, the microcontroller queries the microcontroller bus 310to insure that the microcontroller bus 310 is still functional. If theSDA and SCL lines of the microcontroller bus 310 are not low, themicrocontroller is sure that the microcontroller bus 310 is functionaland proceeds to state 816. If the SDA and SCL lines are not drawn high,then the microcontroller starts to poll the microcontroller bus 310 tosee if it is functional. Moving to state 819, the microcontrollerincrements a counter Y and waits every 22 microseconds. If the counter Yis less than five milliseconds (state 820), the state 814 is reenteredand the microcontroller bus 310 is checked again. If the SDA and SCLlines are low for 5 milliseconds (indicated when, at state 820, thecounter Y exceeds 5 milliseconds), the microcontroller enters state 822and assumes there is a microcontroller bus error. The microcontrollerthen terminates its control of the microcontroller bus 310 (state 824).

If in the state 814, the SDA/SCL lines do not stay low (state 816), themaster microcontroller waits for a response from a slave microcontroller(state 816). If the master microcontroller has not received a response,the microcontroller enters state 826. The microcontroller starts acounter which is incremented every one millisecond. Moving to state 828,if the counter reaches fifty milliseconds, the microcontroller entersstate 830 indicating a microcontroller bus error. The microcontrollerthen resets the microcontroller bus 310 (state 832).

Returning to state 816, if the master microcontroller does receive aresponse in state 816, the microcontroller enters state 818 and receivesthe data from the slave microcontroller. At state 820, the mastermicrocontroller is finished communicating with the slavemicrocontroller.

FIG. 9 is one embodiment of a block diagram illustrating the process bywhich a slave microcontroller communicates with a mastermicrocontroller. Starting in state 900, the slave microcontrollerreceives a byte from a master microcontroller. The first byte of anincoming message always contains the slave address. This slave addressis checked by all of the microcontrollers on the microcontroller bus310. Whichever microcontroller matches the slave address to its ownaddress handles the request.

At a decision state 902, an interrupt is generated on the slavemicrocontroller. The microcontroller checks if the byte received is thefirst received from the master microcontroller (state 904). If thecurrent byte received is the first byte received, the slavemicrocontroller sets a bus time-out flag (state 906). Otherwise, theslave microcontroller proceeds to check if the message is complete(state 908). If the message is incomplete, the microcontroller proceedsto the state 900 to receive the remainder of bytes from the mastermicrocontroller. If at state 908, the slave microcontroller determinesthat the complete message has been received, the microcontrollerproceeds to state 909.

Once the microcontroller has received the first byte, themicrocontroller will continue to check if there is an interrupt on themicrocontroller bus 310. If no interrupt is posted on themicrocontroller bus 310, the slave microcontroller will check to see ifthe bus time-out flag is set. The bus time-out flag is set once a bytehas been received from a master microcontroller. If in the decisionstate 910 the microcontroller determines that the bus time-out flag isset, the slave microcontroller will proceed to check for an interruptevery 10 milliseconds up to 500 milliseconds. For this purpose, theslave microcontroller increments the counter every 10 milliseconds(state 912). In state 914, the microcontroller checks to see if themicrocontroller bus 310 has timed out. If the slave microcontroller hasnot received additional bytes from the master microcontroller, the slavemicrocontroller assumes that the microcontroller bus 310 is hung andresets the microcontroller bus 310 (state 916). Next, the slavemicrocontroller aborts the request and awaits further requests fromother master microcontrollers (state 918).

Referring to the state 909, the bus timeout bit is cleared, and therequest is processed and the response is formulated. Moving to state920, the response is sent a byte at a time. At state 922, the same buscheck is made as was described for the state 814. States 922, 923 and928 form the same bus check and timeout as states 814, 819 and 820. Ifin state 928 this check times out, a bus error exists, and thistransaction is aborted (states 930 and 932).

FIGS. 10A and 10B are flow diagrams showing one process by which theSystem Interface 312 handles requests from other microcontrollers in themicrocontroller network and the ISA bus 226 (FIGS. 4 and 5). The SystemInterface 312 relays messages from the ISA bus 226 to othermicrocontrollers in the network of microcontrollers 225. The SystemInterface 312 also relays messages from the network of microcontrollersto the ISA bus 226.

Referring to FIGS. 10A and 10B, the System Interface 312 initializes allvariables and the stack pointer (state 1000). Moving to state 1002, theSystem Interface 312 starts its main loop in which it performs variousfunctions. The System Interface 312 next checks the bus timeout bit tosee if the microcontroller bus 310 has timed-out (decision state 1004).If the microcontroller bus 310 has timed-out, the System Interface 312resets the microcontroller bus 310 in state 1006.

Proceeding to a decision state 1008, the System Interface 312 checks tosee if any event messages have been received. An event occurs when theSystem Interface 312 receives information from another microcontrollerregarding a change to the state of the system. At state 1010, the SystemInterface 312 sets the event bit in the CSR 709 to one. The SystemInterface 312 also sends an interrupt to the operating system if the CSR709 has requested interrupt notification.

Proceeding to a decision state 1012, the System Interface 312 checks tosee if a device driver for the operating system has input a command tothe CSR. If the System Interface 312 does not find a command, the SystemInterface 312 returns to state 1002. If the System Interface does find acommand from the operating system, the System Interface parses thecommand. For the “allocate command”, the System Interface 312 resets thequeue to the ISA bus 226 resets the done bit in the CSR 709 (state 1016)and sets the CSR Interface Owner ID (state 1016). The Owner ID bitsidentify which device driver owns control of the System Interface 312.

For the “de-allocate command”, the System Interface 312 resets the queueto the ISA bus 226, resets the done bit in the CSR 709, and clears theOwner ID bits (state 1018).

For the “clear done bit command” the System Interface 312 clears thedone bit in the CSR 709 (state 1020). For the “enable interrupt command”the System Interface 312 sets the interrupt enable bit in the CSR 709(state 1022). For the “disable interrupt command”, the System Interface312 sets the interrupt enable bit in the CSR 709 (state 1024). For the“clear interrupt request command”, the System Interface 312 clears theinterrupt enable bit in the CSR 709 (state 1026).

If the request from the operating system was not meant for the SystemInterface 312, the command is intended for another microcontroller inthe network 225. The only valid command remaining is the “messagecommand”. Proceeding to state 1028, the System Interface 312 readsmessage bytes from the request buffer 516. From the state 1028, theSystem Interface 312 proceeds to a decision state 1030 in which theSystem Interface 312 checks whether the command was for itself. If thecommand was for the System Interface 312, moving to state 1032, theSystem Interface 312 processes the command. If the ID did not match aninternal command address, the System Interface 312 relays the commandthe appropriate microcontroller (state 1034) by sending the messagebytes out over the microcontroller bus 310.

FIGS. 11A and 11B are flowcharts showing an embodiment of the functionsperformed by the Chassis controller 318. Starting in the state 1100, theChassis controller 318 initializes its variables and stack pointer.

Proceeding to state 1102, the Chassis controller 318 reads the serialnumbers of the microcontrollers contained on the system board 302 andthe backplane 304. The Chassis controller 318 also reads the serialnumbers for the Canister controllers 324, 326, 328 and 330. The Chassiscontroller 318 stores all of these serial numbers in the NVRAM 322.

Next, the Chassis controller 318 start its main loop in which itperforms various diagnostics (state 1104). The Chassis controller 318checks to see if the microcontroller bus 310 has timed-out (state 1106).If the bus has timed-out, the Chassis controller 318 resets themicrocontroller bus 310 (state 1008). If the microcontroller bus 310 hasnot timed out the Chassis controller proceeds to a decision state 1110in which the Chassis controller 318 checks to see if a user has presseda power switch.

If the Chassis controller 318 determines a user has pressed a powerswitch, the Chassis controller changes the state of the power to eitheron or off (state 1112). Additionally, the Chassis controller logs thenew power state into the NVRAM 322.

The Chassis controller 318 proceeds to handle any power requests fromthe Remote Interface 332 (state 1114). As shown in FIG. 9, a powerrequest message to this microcontroller is received when the arrivingmessage interrupts the microcontroller. The message is processed and abit is set indicating request has been made to toggle power. At state1114, the Chassis controller 318 checks this bit. If the bit is set, theChassis controller 318 toggles the system, i.e., off-to-on or on-to-off,power and logs a message into the NVRAM 322 that the system power haschanged state (state 1116).

Proceeding to state 1118, the Chassis controller 318 checks theoperating system watch dog counter for a time out. If the Chassiscontroller 318 finds that the operating system has failed to update thetimer, the Chassis controller 318 proceeds to log a message with theNVRAM 322 (state 1120). Additionally, the Chassis controller 318 sendsan event to the System Interface 312 and the Remote Interface 332.

Since it takes some time for the power supplies to settle and producestable DC power, the Chassis controller delays before proceeding tocheck DC (state 1122).

The Chassis controller 318 then checks for changes in the canisters258-264 (state 1124), such as a canister being inserted or removed. If achange is detected, the Chassis controller 318 logs a message to theNVRAM 322 (state 1126). Additionally, the Chassis controller 318 sendsan event to the System Interface 312 and the Remote Interface 332.

The Chassis controller 318 proceeds to check the power supply for achange in status (state 1128). The process by which the Chassiscontroller 318 checks the power supply is described in further detail inthe discussion for FIG. 12.

The Chassis controller then checks the temperature of the system (state1132). The process by which the Chassis controller 318 checks thetemperature is described in further detail in the discussion for FIG.13.

At state 1136, the Chassis controller 318 reads all of the voltage levelsignals. The Chassis controller 318 saves these voltage levels values inan internal register for reference by other microcontrollers.

Next, the Chassis controller 318 checks the power supply signals forAC/DC changes (state 1138). If the Chassis controller 318 detects achange in the Chassis controller 318, the Chassis controller 318 logs amessage to the NVRAM 322 (state 1140). Additionally, the Chassiscontroller 318 sends an event to the System Interface 312 and the RemoteInterface 332 that a AC/DC signal has changed. The Chassis controller318 then returns to state 1104 to repeat the monitoring process.

FIG. 12 is a flowchart showing one process by which the Chassiscontroller 318 checks the state of the redundant power supplies termednumber 1 and 2. These power supplies are monitored and controlled by thechassis controller 318 through the signal lines shown in FIG. 5A. When apower supply fails or requires maintenance, the other supply maintainspower to the computer 100. To determine whether a power supply isoperating properly or not, its status of inserted or removed (bymaintenance personnel) should be ascertained. Furthermore, a change instatus should be recorded in the NVRAM 322. FIG. 12 describes in greaterdetail the state 1128 shown in FIG. 11B.

Starting in state 1202, the Chassis controller 318 checks the powersupply bit. If the power supply bit indicates that a power supply shouldbe present, the Chassis controller checks whether power supply “number1” has been removed (state 1204). If power supply number 1 has beenremoved, the chassis microcontroller 318 checks whether its internalstate indicates power supply number one should be present. If theinternal state was determined to be present, then the slot is checked tosee whether power supply number 1 is still physically present (state1204). If power supply number 1 has been removed, the PS_PRESENT#1 bitis changed to not present (state 1208). The Chassis controller 318 thenlogs a message in the NVRAM 322.

Referring to state 1206, if the PS_PRESENT#1 bit indicates that powersupply number 1 is not present, the Chassis controller 318 checkswhether power supply number 1 has been inserted (i.e., checks to see ifit is now physically present) (state 1206). If it has been inserted, theChassis controller 318 then logs a message into the NVRAM 322 that thepower supply number 1 has been inserted (state 1210) and changes thevalue of PS_PRESENT#1 to present.

After completion, states 1204, 1206, 1208, and 1210 proceed to state1212 to monitor power supply number 2. The Chassis controller 318 checkswhether the PS_PRESENT#2 bit is set to present. If the PS_PRESENT#2 bitindicates that power supply “number 2” should be there, the Chassiscontroller 318 proceeds to state 1224. Otherwise, the Chassis controller318 proceeds to state 1226. At state 1224, the Chassis controller 318checks if power supply number 2 is still present. If power supply number2 has been removed, the Chassis controller 318 logs in the NVRAM 322that power supply number 2 has been removed (state 1228). The chassiscontroller also changes the value of PS_PRESENT#2 bit to not present.

Referring to decision state 1226, if the PS_PRESENT#2 bit indicates thatno power supply number 2 is present, the Chassis controller 318 checksif power supply number 2 has been inserted. If so, the Chassiscontroller 318 then logs a message into the NVRAM 322 that power supplynumber 2 has been inserted and changes the value of PS_PRESENT#2 topresent (state 1230). After completion of states 1224, 1226, 1228, and1230, the chassis controller 318 proceeds to state 1232 to monitor theAC/DC power supply changed signal.

If in decision state 1234 the Chassis controller 318 finds that theAC/DC power supply changed signal from the power supplies is asserted,the change in status is recorded in state 1236. The Chassis controller318 continues the monitoring process by proceeding to the state 1132 inFIG. 11B.

FIG. 13 is a flowchart showing one process by which the Chassiscontroller 318 monitors the temperature of the system. As shown in FIG.5A, the Chassis controller 318 receives temperature detector signallines from five temperature detectors located on the backplane and themotherboard. If either component indicates it is overheating,preventative action may be taken manually, by a technician, orautomatically by the network of microcontrollers 225. FIG. 13 describesin greater detail the state 1132 shown in FIG. 11B.

To read the temperature of the Chassis, the Chassis controller 318 readsthe temperature detectors 502, 504, and 506 (state 1300). In theembodiment of the invention shown in FIG. 13 there are five temperaturedetectors (two temperature detectors not shown). Another embodimentincludes three temperature detectors as shown.

The Chassis controller 318 checks the temperature detector 502 to see ifthe temperature is less than −25° C. or if the temperature is greaterthan or equal to 55° C. (state 1308). Temperatures in this range areconsidered normal operating temperatures. Of course, other embodimentsmay use other temperature ranges. If the temperature is operating insidenormal operating boundaries, the Chassis controller 318 proceeds tostate 1310. If the temperature is outside normal operating boundaries,the Chassis controller 318 proceeds to state 1312. At state 1312, theChassis controller 318 evaluates the temperature a second time to checkif the temperature is greater than or equal to 70° C. or less than orequal to −25° C. If the temperature falls below or above outside ofthese threshold values, the Chassis controller proceeds to state 1316.Temperatures in this range are considered so far out of normal operatingtemperatures, that the computer 100 should be shutdown. Of course, othertemperature ranges may be used in other embodiments.

Referring to state 1316, if the temperature level reading is critical,the Chassis controller 318 logs a message in the NVRAM 322 that thesystem was shut down due to excessive temperature. The Chassiscontroller 318 then proceeds to turn off power to the system in state1320, but may continue to operate from a bias or power supply.

Otherwise, if the temperature is outside normal operating temperatures,but only slightly deviant, the Chassis controller 318 sets a bit in thetemperature warning status register (state 1314). Additionally, theChassis controller 318 logs a message in the NVRAM 322 that thetemperature is reaching dangerous levels (state 1318).

The Chassis controller 318 follows the aforementioned process for eachtemperature detector on the system. Referring back to state 1310, whichwas entered after determining a normal temperature from one of thetemperature detectors, the Chassis controller 318 checks a loopingvariable “N” to see if all the sensors were read. If all sensors werenot read, the Chassis controller 318 returns to state 1300 to readanother temperature detector. Otherwise, if all temperature detectorswere read, the Chassis controller 318 proceeds to state 1322. At state1322, the Chassis controller 318 checks a warning status register (notshown). If no bit is set in the temperature warning status register, theChassis controller 318 returns to the state 1136 in FIG. 11B. If theChassis controller 318 determines that a bit in the warning statusregister was set for one of the sensors, the Chassis controller 318proceeds to recheck all of the sensors (state 1324). If the temperatureof the sensors are still at a dangerous level, the Chassis Controller318 maintains the warning bits in the warning status register. TheChassis controller 318 then proceeds to the state 1136 (FIG. 11B). Atstate 1324, if the temperatures of the sensors are now at normaloperating values, the Chassis controller 318 proceeds to clear all ofthe bits in the warning status register (state 1326). After clearing theregister, the Chassis controller 318 proceeds to state 1328 to log amessage in the NVRAM 322 that the temperature has returned to normaloperational values, and the Chassis controller 318 proceeds to the state11136 (FIG. 11B).

FIGS. 14A and 14B are flowcharts showing the functions performed by oneembodiment of the CPU A controller 314. The CPU A controller 314 islocated on the system board 302 and conducts diagnostic checks for: amicrocontroller bus timeout, a manual system board reset, a low systemfan speed, a software reset command, general faults, a request to writeto flash memory, checks system flag status, and a system fault.

The CPU A controller 314, starting in state 1400, initializes itsvariables and stack pointer. Next, in state 1402 the CPU A controller314 starts its main loop in which it performs various diagnostics whichare described below. At state 1404, the CPU A controller 314 checks themicrocontroller bus 310 for a time out. If the microcontroller bus 310has timed out, the CPU A controller 314 resets the microcontroller bus310 (state 1406). From either state 1404 or 1406, the CPU A controller314 proceeds to check whether the manual reset switch (not shown) ispressed on the system board 302 (decision state 1408). If the CPU Acontroller 314 determines that the manual reset switch is pressed, theCPU A controller resets system board by asserting a reset signal (state1410).

From either state 1408 or 1410, the CPU A controller 314 proceeds tocheck the fan speed (decision state 1412). If any of a number of fansspeed is low (see FIG. 15 and discussion below), the CPU A controller314 logs a message to NVRAM 322 (state 1414). Additionally, the CPU Acontroller 314 sends an event to the Remote Interface 334 and the SystemInterface 312. The CPU A controller 314 next proceeds to check whether asoftware reset command was issued by either the computer 100 or theremote computer 132 (state 1416). If such a command was sent, the CPU Acontroller 314 logs a message in NVRAM 322 that system softwarerequested the reset command (state 1418). Additionally, the CPU Acontroller 314 also resets the system bus 202.

From either state 1416 or 1418, the CPU A controller 314 checks theflags bits (not shown) to determine if a user defined system faultoccurred (state 1420). If the CPU A controller 314 determines that auser defined system fault occurred, the CPU A controller 314 proceeds todisplay the fault on an LCD display 512 (FIG. 5B) (state 1422).

From either state 1420 or 1422 the CPU A controller 314 proceeds to astate 1424 (if flash bit was not enabled) to check the flash enable bitmaintained in memory on the CPU B controller 316. If the flash enablebit is set, the CPU A controller 314 displays a code for flash enabledon the LCD display 512. The purpose of the flash enable bit is furtherdescribed in the description for the CPU B controller 316 (FIG. 16).

From either state 1424 or 1426 (if the flash bit was not enabled), theCPU A controller 314 proceeds to state 1428 and checks for systemfaults. If the CPU A controller 314 determines that a fault occurred,the CPU A controller 314 displays the fault on the LCD display 512(state 1430). From state 1428 if no fault occurred, or from state 1430,the CPU A controller 314 proceeds to the checks the system status flaglocated in the CPU A controller's memory (decision state 1432). If thestatus flag indicates an error, the CPU A controller 314 proceeds tostate 1434 and displays error information on the LCD display 512.

From either state 1432 or 1434, the CPU controller proceeds to state1402 to repeat the monitoring process.

FIG. 15 is a flowchart showing one process by which the CPU A controller314 monitors the fan speed. FIG. 15 is a more detailed description ofthe function of state 1412 in FIG. 14A. Starting in state 1502, the CPUA controller 314 reads the speed of each of the fans 1506, 1508, and1510. The fan speed is processed by a Fan Tachometer Signal Mux 508(also shown in FIG. 5B) which updates the CPU A controller 314. The CPUA controller 314 then checks to see if a fan speed is above a specifiedthreshold (state 1512). If the fan speed is above the threshold, the CPUA controller 314 proceeds to state 1514. Otherwise, if the fan speed isoperating below a specified low speed limit, the CPU A controller 314proceeds to state 1522.

On the other hand, when the fan is operating above the low speed limitat state 1514, the CPU A controller 314 checks the hot_swap_fan register(not shown) if the particular fan was hot swapped. If the fan was hotswapped, the CPU A controller 314 proceeds to clear the fan's bit inboth the fan_fault register (not shown) and the hot_swap_fan register(state 1516). After clearing these bits, the CPU A controller 314 checksthe fan fault register (state 1518). If the fan fault register is allclear, the CPU A controller 314 proceeds to set the fan to low speed(state 1520) and logs a message to the NVRAM 322. The CPU A controller314 then proceeds to state 1536 to check for a temperature warning.

Now, referring back to state 1522, if a fan speed is below a specifiedthreshold limit, the CPU A controller 314 checks to see if the fan'sspeed is zero. If the fan's speed is zero, the CPU A controller 314 setsthe bit in the hot_swap_fan register in state 1524 to indicate that thefan has a fault and should be replaced. If the fan's speed is not zero,the CPU A controller 314 will proceed to set a bit in the fan_faultregister (state 1526). Moving to state 1528, the speed of any fans stilloperating is increased to high, and a message is written to the NVRAM322.

In one alternative embodiment, the system self-manages temperature asfollows: from either state 1520 or 1528, the CPU A controller 314 movesto state 1536 and checks whether a message was received from the Chassiscontroller 318 indicating temperature warning. If a temperature warningis indicated, and if there are no fan faults involving fans in thecooling group associated with the warning, the speed of fans in thatcooling group is increased to provide more cooling capacity (state1538).

Proceeding to state 1530 from either state 1536 or 1538, the CPU Acontroller 314 increments a fan counter stored inside of microcontrollermemory. If at state 1531, there are more fans to check, the CPU Acontroller 314 returns to state 1502 to monitor the speed of the otherfans. Otherwise, the CPU controller 314 returns to state 1416 (FIG. 14).

FIG. 16 is one embodiment of a flow diagram showing the functionsperformed by the CPU B controller 316. The CPU B controller 316 scansfor system faults, scans the microcontroller bus 310, and provides flashenable. The CPU B controller 316, starting at state 1600, initializesits variables and stack pointer.

After initializing its internal state, the CPU B controller 316 enters adiagnostic loop at state 1602. The CPU B controller 316 then checks themicrocontroller bus 310 for a time out (decision state 1604). If themicrocontroller bus 310 has timed out, the CPU B controller 316 resetsthe microcontroller bus 310 in state 1606. If the microcontroller bus310 has not timed out (state 1604) or after state 1606, the CPU Bcontroller 316 proceeds to check the system fault register (not shown)(decision state 1608).

If the CPU B controller 316 finds a system fault, the CPU B controller316 proceeds to log a message into the NVRAM 322 stating that a systemfault occurred (state 1610). The CPU B controller 316 then sends anevent to the System Interface 312 and the Remote Interface 332.Additionally, the CPU B controller 316 turns on one of a number of LEDindicators 518 (FIG. 5B).

If no system fault occurred, or from state 1610, the CPU B controller316 scans the microcontroller bus 310 (decision state 1612). If themicrocontroller bus 310 is hung then the CPU B controller 316 proceedsto flash an LED display 512 that the microcontroller bus 310 is hung(state 1614). Otherwise, if the bus is not hung the CPU B controller 316then proceeds to state 1624.

The CPU B controller 316 proceeds to check for a bus stop bit time out(decision state 1624). If the stop bit has timed out, the CPU Bcontroller 316 generates a stop bit on the microcontroller bus for errorrecovery in case the stop bit is inadvertently being held low by anothermicrocontroller (state 1626).

From either state 1624 or 1626, the CPU B controller 316 proceeds tocheck the flash enable bit to determine if the flash enable bit (notshown) is set (state 1628). If the CPU B controller 316 determines thatthe flash enable bit is set (by previously having received a messagerequesting it), the CPU B controller 316 proceeds to log a message tothe NVRAM 322 (state 1630). A flash update is performed by the BIOS ifthe system boot disk includes code to update a flash memory (not shown).The BIOS writes new code into the flash memory only if the flash memoryis enabled for writing. A software application running on the CPUs 200can send messages requesting that BIOS flash be enabled. At state 1630,the 12 Volts needed to write the flash memory is turned on or leftturned on. If the flash enable bit is not on, control passes to state1629, where the 12 Volts is turned off, disabling writing of the flashmemory.

From either state 1629 or 1630, the CPU B controller 316 proceeds torepeat the aforementioned process of monitoring for system faults (state1602).

FIG. 17 is one embodiment of a flowchart showing the functions performedby the Canister controllers 324, 326, 328 and 330 shown in FIGS. 4 and5. The Canister controllers 324, 326, 328 and 330 examine canister fanspeeds, control power to the canister, and determine which canisterslots contain cards. The Canister controllers 324-330, starting in state1700, initialize their variables and stack pointers.

Next, in state 1702 the Canister controllers 324-330 start their mainloop in which they performs various diagnostics, which are furtherdescribed below. The Canister controllers 324-330 check themicrocontroller bus 310 for a time out (state 1704). If themicrocontroller bus 310 has timed out, the Canister controllers 324-330reset the microcontroller bus 310 in state 1706. After the Canistercontroller 324-330 reset the microcontroller bus 310, or if themicrocontroller bus 310 has not timed out, the Canister controllers324-330 proceed to examine the speed of the fans (decision state 1708).As determined by tachometer signal lines connected through a fanmultiplexer 508 (FIG. 5), if either of two canister fans is below thelower threshold, the event is logged, an event is sent to the SystemInterface 312 and, speed, in a self-management embodiment, the fan speedis set to high. The Canister controllers 324-330 check the fan speedagain, and if they are still low the canister controlling 324-330 signala fan fault and register an error message in the NVRAM 322 (state 1710).

If the Canister controller received a request message to turn on or offcanister power, a bit would have been previously set. If the Canistercontrollers 324-330 find this bit set (state 1712), they turn the powerto the canister on, and light the canister's LED. If the bit is cleared,power to the canister is turned off, as is the LED (state 1714).

Next, the Canister controllers 324-330 read a signal for each slot whichindicates whether the slot contains an adapter (state 1716). TheCanister controllers 324-330 then returns to the state 1702, to repeatthe aforementioned monitoring process.

FIG. 18 is one embodiment of a flowchart showing the functions performedby the System Recorder controller 320. The System Recorder controller320 maintains a system log in the NVRAM 322. The System Recorder 320starting in state 1800 initializes its variables and stack pointer.

Next, at state 1802 the System Recorder 320 starts its main loop inwhich the System Recorder 320 performs various functions, which arefurther described below. First, the System Recorder 320 checks themicrocontroller bus 310 for a time out (state 1804). If themicrocontroller bus 310 has timed out, the System Recorder 320 resetsthe microcontroller bus 310 in state 1806. After the System Recorder 320resets the bus, or if the microcontroller bus 310 has not timed out, theSystem Recorder 320 checks to see if another microcontroller hadrequested the System Recorder 320 to reset the NVRAM 322 (state 1808).If requested, the System Recorder 320 proceeds to reset all the memoryin the NVRAM 322 to zero (decision state 1810). After resetting theNVRAM 322, or if no microcontroller had requested such a reset, theSystem Recorder 320 proceeds to a get the real time clock every secondfrom a timer chip 520 (FIG. 5A) (decision state 1812).

From time to time, the System Recorder 320 will be interrupted by thereceipt of messages. When these messages are for storing data in theNVRAM 322, they are carried out as they are received and the messagesare stored in the NVRAM 322. Thus, there is no state in the flow of FIG.18 to explicitly store messages. The System Recorder then returns to thestate 1802 to repeat the aforementioned monitoring process.

While the above detailed description has shown, described, and pointedout the fundamental novel features of the invention as applied tovarious embodiments, it will be understood that various omissions andsubstitutions and changes in the form and details of the systemillustrated by be made by those skilled in the art, without departingfrom the intent of the invention.

Header File for Global Memory Addresses

#ifndef SDL_TYPES #ifndef FAR_POINTERS typedef unsigned char*BYTEADDRESS; typedef unsigned short *WORDADDRESS; typedef unsigned long*LONGADDRESS; typedef char *SBYTEADDRESS; typedef short *SWORDADDRESS;typedef long *SLONGADDRESS; #else typedef unsigned long BYTEADDRESS;typedef unsigned long WORDADDRESS; typedef unsigned long LONGADDRESS;typedef unsigned long SBYTEADDRESS; typedef unsigned long SWORDADDRESS;typedef unsigned long SLONGADDRESS; #endif #define SDL_TYPES 1 #endif /* */ /* $Module CS9000WS.SDL$ */ /*  */ /* Copyright 1996 */ /* ByNetFRAME Systems Inc. */ /*  Milpitas, California U.S.A. */ /*  */ /*$Author: Ken Nguyen $ */ /* $Date: 31 Mar 1997 15:28:08 $ */ /*$Revision */ /*  */ /* $Description$ */ /* This file contains theNetFRAME Wire Service message and interface definition. */ /*  for theCS9000 */ /* $EndDescription$ */ /*  */ /*  Revision History */ /* $Log: P:/inc/cs9000ws.sdl $ */ /*  */ /*  Rev 1.16  31 Mar 1997 15:28:08  KenNguyen */ /*  Added WSEvent variables, Severity bytes and WS commands.*/ /*  */ /*  Rev 1.15  28 Jan 1997 16:31:32  Ken Nguyen */ /*  Cleanedup SDL file */ /*  Added Buffer Event Commands and Event ID Number. *//*  */ /*  Rev 1.14  27 Nov 1996 14:10:12  Ken Nguyen */ /*  Addedcommands for Raptor 8 */ /*  Added WSEVENT_CPU event. */ /*  */ /*  Rev1.13  25 Oct 1996 16:48:18  Ken Nguyen */ /*  Fixed a Problem ofCanister Fan Fault Status. */ /*  */ /*  Rev 1.10  10 Oct 1996 16:33:04 Ken Nguyen */ /*  Added a command to count Log entry. */ /*  */ /*  Rev1.9  30 Sep 1996 18:42:50  Ken Nguyen */ /*  Added Canister FaultCommands */ /*  */ /*  Rev 1.8  30 Sep 1996 17:34:16  Karl Johnson */ /* Added definitions for remote interface serial protocol */ /*  AddedNVRAM error counter */ /*  */ /*  Rev 1.7  13 Sep 1996 11:22:22  KenNguyen */ /* Corrected Temperature data length */ /*  */ /*  Rev 1.6  09Sep 1996 17:24:48  Karl Johnson */ /*  Added WS_SYSLOG_CLOCK - the clockused by the log recorder to time stamp */ /*  */ /*  Rev 1.5  20 Aug1996 01:08:36  Karl Johnson */ /*  Added screen event and correctedBOOTDEVS name. */ /*  */ /*  Rev 1.4  01 Aug 1996 15:32:50  Karl Johnson*/ /*  Cleanup and added new status values. */ /*  */ /*  Rev 1.3  26Jul 1996 17:14:38  Karl Johnson */ /*  Reduced maximum number of eventtypes. */ /*  Added a Success Status. */ /*  */ /*  Rev 1.2  08 Jul 199615:57:32  Karl Johnson */ /*  Changed read write bit in datatypedefinition. */ /*  Added WS_BOOTDEVS missed in translatingspecification. */ /*  */ /*  Rev 1.1  19 Jun 1996 14:15:28  Karl Johnson*/ /*  Added LCD low level access items. */ /*  */ /*  Rev 1.0  18 Jun1996 14:06:58  Karl Johnson */ /*  Initial revision. */ /* */ /************************************************ */ /*  This is the WireService Message format */ #ifndef PIC_PROCESSOR struct WSMessage  { unsigned char ToProcesor;  unsigned char Type_RW;  unsigned charAddressLow;  unsigned char AddressHi;  unsigned char WriteLength; /* WriteData  BLOCK_BYTE 0  ; Write data stream goes here */  }; #defineWSMessage_S 5 struct WSResponse  {  unsigned char FromProcesor; unsigned char ReadLength; /*  ReadData  BLOCK_BYTE 0  ; Read datastream goes here */  unsigned char Status;  }; #define WSResponse_S 3#endif /*  */ /*  Wire Service Local Interface Definitions */ /*  */ /*Command (CSR Write) Register definitions */ #define WSCMD_RequestInt0x80 /* Request interrupt on command complete */ #define WSCMD_Allocate10x01 /* Allocate interface as ID 1 */ #define WSCMD_Allocate2 0x02 /*Allocate interface as ID 2 */ #define WSCMD_Allocate3 0x03 /* Allocateinterface as ID 3 */ #define WSCMD_Allocate4 0x04 /* Allocate interfaceas ID 4 */ #define WSCMD_Allocate5 0x05 /* Allocate interface as ID 5 */#define WSCMD_Allocate6 0x06 /* Allocate interface as ID 6 */ #defineWSCMD_Allocate7 0x07 /* Allocate interface as ID 7 */ #defineWSCMD_Deallocate 0x10 /* Deallocate interface */ #defineWSCMD_EnableInts 0x11 /* Enable interrupts for events */ #defineWSCMD_DisableInts 0x12 /* Disable interrupts for events */ #defineWSCMD_Message 0x13 /* Process message in FIFO and set done */ #defineWSCMD_ClearDone 0x20 /* Clear done bit & error bit and clear FIFOs */#define WSCMD_ClearIntReq 0x21 /* Clear Interrupt Request bit */ /* (Must poll WSTS_IntReq => 0 for completion ) */ #define WSCMD_Reset 0x0a5 /* Reset interface */ #define WSCMD_DiagMode 0x05a /* Enter Diagnosticmode */ #define WSCMD_ExitDiagMode 0x00 /* Exit Diagnostic mode */ /*Status (CSR Read) Register definitions */ #define WSSTS_Error 0x80  /*Error processing command */ #define WSSTS_IntEna 0x40  /* EventInterrupts are enabled */ #define WSSTS_Events 0x20  /* One or moreevents occurred */ #define WSSTS_Done 0x10  /* Message command is done*/ #define WSSTS_IntReq 0x08  /* Interrupt is being requested */ #defineWSSTS_AllocMask 0x07 /* ID of owner of interface */ /* IO Addresses ofWire Service Local Interface */ #define WSLOC_Data 0x0CC0 #defineWSLOC_CSR 0x0CC1 /******************************************************************** *//* These are the data type definitions */ #define WSTYPE_BIT 0x01#define WSTYPE_BYTE 0x02 #define WSTYPE_STRING 0x03 #define WSTYPE_LOG0x04 #define WSTYPE_EVENT 0x05 #define WSTYPE_QUEUE 0x06 #defineWSTYPE_ARRAY 0x07 #define WSTYPE_LOCK 0x08 #define WSTYPE_SCREEN 0x09#define WSOP_READ 0x80 #define WSOP_WRITE 0x00 #define WSEVENT_CAN_CHG0x01 #define WSEVENT_PS_CHG 0x02 #define WSEVENT_QUEUE 0x03 #defineWSEVENT_TEMP 0x04 #define WSEVENT_ACOK 0x05 #define WSEVENT_DCOK 0x06#define WSEVENT_FAN 0x07 #define WSEVENT_SCREEN 0x08 #define WSEVENT_CPU0x09 #define WSEVENT_OS_TimeOut 0x0A /* Event of OS's Timer is timed out*/ #define WSEVENT_PCI_TimeOut 0x0B /* Event of Power ON/OFF PCI Slot istimed out */ #define WSEVENT_CALLOUT 0x0C /* Call Out Event */ #defineWSEVENT_MAXVALUE 0x0F /* Make sure no event values exceed this value */#define WSERR_NONE 0x00 /* No error occurred */ #define WSERR_NONODE0x01 /* Slave addressed did not respond */ #define WSERR_NOADDRESS 0x02/* Slave responded that it had no such type/address */ #defineWSERR_CORRUPTED 0x03 /* Message or Response is not valid */ #defineWSERR_UNDERRUN 0x04 /* Message could not be completely transmitted orreceived */ #define WSERR_DATACHECK 0x05 /* Message data checksumreceived incorrectly ( try again if possible ) */ #defineWSERR_OPERATION 0x06 /* Slave operation not possible (e.g. Wr to R/O) */#define WSERR_NODATA 0x07 /* Slave responded no data available ataddress (queue/log) */ #define WSPID_SYSLOG 0x01 #define WSPID_BACKPLANE0x02 #define WSPID_SYSTEMA 0x03 #define WSPID_SYSTEMB 0x04 #defineWSPID_LOCAL_IF 0x10 #define WSPID_REMOTE_IF 0x11 #define WSPID_CANISTER10x20 #define WSPID_CANISTER2 0x21 #define WSPID_CANISTER3 0x22 #defineWSPID_CANISTER4 0x23 /******************************************************************** *//*  Wire Service Remote Interface Protocol Constants */ #define WSRI_SOM0x7B  /* Serial Start Of Message */ #define WSRI_EOM 0x7D  /* Serial EndOf Message */ #define WSRI_SUB 0x5C  /* Serial Substitute next character*/ #define WSRI_EVT 0x5E  /* Serial Event indicator */ #defineWSRI_REQ_IDENTIFY 0x01 /* Request Identity and reset sequence */ #defineWSRI_REQ_SECURE 0x02 /* Request to enter Security mode (logon) */#define WSRI_REQ_UNSECURE 0x03 /* Request to leave Security mode */#define WSRI_REQ_MESSAGE 0x04 /* Request contains WS message to process*/ #define WSRI_REQ_POLL 0x05 /* Request status */ #define WSRI_STAT_OK0x01  /* Request OK return data valid */ #define WSRI_STAT_OK_EVENT 0x02/* Request OK return data valid ( Event(s) pending ) */ #defineWSRI_STAT_E_SEQUENCE  0x03 /* Request not in Sequence */ #defineWSRI_STAT_E_DATACHECK  0x03 /* Request check byte not correct */ #defineWSRI_STAT_E_FORMAT 0x04 /* Request format incorrect */ #defineWSRI_STAT_E_SECURE 0x05 /* Request requires Security mode */ /******************************************************************** *//*  Wire Service Log Message Constants */ /*  */ /*  First byte of logmessage data: Severity Level Byte */ #define WSLOG_LEVEL_UNKNOWN  0x00/* Unknown */ #define WSLOG_LEVEL_INFO 0x10 /* Informational */ #defineWSLOG_LEVEL_WARN 0x20 /*  Warning */ #define WSLOG_LEVEL_ERROR 0x30 /* Error */ #define WSLOG_LEVEL_FATAL 0x40 /*  Severe/Fatal Error */ /* Second byte of log message data: Source/Encoding Byte */ /*  - whichentity logged the entry in the 4 high bits */ /*  - which type ofencoding of the message is used in the 4 low bits of the byte. */#define WSLOG_SRC_INTERNAL  0x00 /*  Wire Service Internal */ #defineWSLOG_SRC_OBDIAG 0x10 /*  Onboard Diagnostics */ #defineWSLOG_SRC_EXDIAG 0x20 /*  External Diagnostics */ #define WSLOG_SRC_BIOS0x30 /*  BIOS */ #define WSLOG_SRC_DOS 0x40 /*  DOS */ #defineWSLOG_SRC_WIN 0x50 /*  Windows,Win95 */ #define WSLOG_SRC_WINNT 0x60 /* Windows/NT */ #define WSLOG_SRC_NETWARE  0x70 /*  NetWare */ #defineWSLOG_TYPE_BINARY 0x00 /*  Message data is Binary */ #defineWSLOG_TYPE_ASCII 0x10 /*  Message data is ASCII */ #defineWSLOG_TYPE_UNICODE  0x20 /*  Message data is Unicode */ /********************************************************** */ /*  This isthe Wire Service addresses for named items. */ /*  */ /*  Addresses arecomposed of three parts: Processor ID, Data Type and Subaddress */ /* In this table the address is encoded as a 4 bytes in hexadecimalnotation: */ /*  PPTTAAAAh where PP is the processor ID, TT is the datatype and AL AH is the */ /*  2 byte subaddress. Processor ID's 00 and 20are special, 00 applies to all */ /*  processors and 20 applies to allcanister processors. */ /*  */ /* PPTTALAH */ #define WS_DESCRIPTION0x00030100 /* (S) Wire Service Processor Type/Description */ #defineWS_REVISION 0x00030200 /* (S) Wire Service Software Revision/Date Info*/ #define WS_WDOG_CALLOUT 0x01010200 /* (L) This is a bit controllingcallout on a watchdog timeout. */ #define WS_WDOG_RESET 0x01010300 /*(L) This is a bit controlling system on a watchdog timeout. */ #defineWS_NVRAM_RESET 0x01020100 /* (B) Trigger to reset NVRAM Data */ #defineWS_SYS_BOOTFLAG1 0x01020200 /* (B) System Boot Flag 1 */ #defineWS_SYS_BOOTFLAG2 0x01020300 /* (B) System Boot Flag 2 */ #defineWS_SYS_BOOTFLAG3 0x01020400 /* (B) System Boot Flag 3 */ #defineWS_SYS_BOOTFLAG4 0x01020500 /* (B) System Boot Flag 4 */ #defineWS_SYS_XDATA_KBYTES  0x01020600 /* (B) Size of the WS_SYS_XDATA inkilobytes */ #define WS_NVRAM_FAULTS 0x01020700 /* (B) Faults detectedin NVRAM Data */ #define WS_SYS_XDATA 0x01070000 /* Byte Array forstorage of arbitrary external data in NVRAM */ #define WS_SYS_LOG0x01040000 /* System Log */ #define WS_RI_QUEUE 0x01060100 /* (Q) Queueof data going to Remote Interface */ #define WS_SI_QUEUE 0x01060200 /*(Q) Queue of data going to System Interface */ #define WS_SYS_SCREEN0x01090000 /* System Screen */ #define WS_CALLOUT_SCRIPT 0x01030300 /*(S) The callout script for remote notification */ #define WS_PASSWORD0x01030400 /* (S) The access password for Wire Service */ #defineWS_SYS_BP_SERIAL 0x01030500 /* (S) Last known Back Plane serial data */#define WS_SYS_CAN_SERIAL1 0x01030600 /* (S) Last known Canister 1Serial data */ #define WS_SYS_CAN_SERIAL2 0x01030700 /* (S) Last knownCanister 2 Serial data */ #define WS_SYS_CAN_SERIAL3 0x01030800 /* (S)Last known Canister 3 Serial data */ #define WS_SYS_CAN_SERIAL40x01030900 /* (S) Last known Canister 4 Serial data */ #defineWS_SYS_RI_SERIAL 0x01031600 /* (S) Last known Remote Interface serialdata */ #define WS_SYS_SB_SERIAL 0x01031700 /* (S) Last known SystemBoard serial data */ #define WS_SYS_PS_SERIAL1 0x01031800 /* (S) Lastknown Power Supply 1 serial data */ #define WS_SYS_PS_SERIAL2 0x01031900/* (S) Last known Power Supply 2 serial data */ #defineWS_SYS_PS_SERIAL3 0x01031a00 /* (S) Last known Power Supply 3 serialdata */ #define WS_NAME 0x01031b00 /* (S) System Identifying Name */#define WS_BOOTDEVS 0x01031c00 /* (S) BIOS Boot drive information */#define WS_SYS_LOG_CLOCK 0x01031d00 /* (S) Current time from logtimestamp clock (seconds) */ #define WS_SYS_LOG_COUNT 0x01031e00 /* (S)Number of Log Entry */ #define WS_MODEM_INIT 0x01031f00 /* (S) Modeminitialization string */ #define WS_EVENT_ID01 0x01032000 /* (S)Canister Change Event */ #define WS_EVENT_ID02 0x01032100 /* (S) PowerSupply Change Event */ #define WS_EVENT_ID03 0x01032200 /* (S) QueueEvent */ #define WS_EVENT_ID04 0x01032300 /* (S) Temp Warn or Shut Event*/ #define WS_EVENT_ID05 0x01032400 /* (S) ACOK Change Event */ #defineWS_EVENT_ID06 0x01032500 /* (S) DCOK Change Event */ #defineWS_EVENT_ID07 0x01032600 /* (S) Fan Fault Event */ #define WS_EVENT_ID080x01032700 /* (S) Screen Event */ #define WS_EVENT_ID09 0x01032800 /*(S) CPU Fault Event */ #define WS_EVENT_ID0A 0x01032900 /* (S)OS_TimeOut Event */ #define WS_CALLOUT_MASK 0x01034000 /* (S) Call OutMasking string */ #define WS_BIOS_REV 0x01034100 /* (S) Storage ofcurrent BIOS Revision */ #define WS_SYS_POWER 0x02010100 /* (L) Controlssystem master power S4_POWER_ON */ #define WS_SYS_REQ_POWER 0x02010200/* (L) Set to request main power on */ #define WS_BP_P12V 0x02020100 /*(B) Analog Measure of +12 volt main supply */ #define WS_BP_P3V0x02020200 /* (B) Analog Measure of +3.3 volt main supply */ #defineWS_BP_N12V 0x02020300 /* (B) Analog Measure of −12 volt main supply */#define WS_BP_P5V 0x02020400 /* (B) Analog Measure of +5 volt mainsupply */ #define WS_BP_VREF 0x02020500 /* (B) Analog Measure of VREF */#define WS_SYS_BP_TYPE 0x02020600 /* (B) Type of system backplanecurrently only two types Type 0= 4 canister (small) and Type 1= 8canister (large) */ #define WS_SYS_CAN_PRES 0x02020700 /* (B) Presencebits for canisters (LSB=1, MSB=8) */ #define WS_SYS_PS_ACOK 0x02020800/* (B) Power supply ACOK status (LSB=1, MSB=3) */ #define WS_SYS_PS_DCOK0x02020900 /* (B) Power supply DCOK status (LSB=1, MSB=3) */ #defineWS_SYS_PS_PRES 0x02020a00 /* (B) Presence bits for power supplies(LSB=1, MSB=3) */ #define WS_SYS_RSTIMER 0x02020b00 /* (B) Used to delayreset/run until power stabilized */ #define WS_SYS_TEMP_SHUT 0x02020c00/* (B) Shutdown temperature. Initialized to ??? */ #defineWS_SYS_TEMP_WARN 0x02020d00 /* (B) Warning temperature. Initialized to??? */ #define WS_SYS_WDOG 0x02020e00 /* (B) System watchdog timer */ /* First issues following command in phase 2 */ #defineWS_OS_RESOLUTION_16  0x04020600 /* (B) Set Resolution (0,1,2,3) ofTimer1 */ #define WS_OS_COUNTER_16 0x04020700 /* (B) Set Counter from(00 - FFh) of Timer1 */ /*  If either operation's failed that it willresponse error code “02h” back, then try raptor 8 and future command */#define WS_OS_RESOLUTION_8 0x02020f00 /* (B) Set Resolution (0,1,2,3) ofTimer1 */ #define WS_OS_COUNTER_8 0x02021000 /* (B) Set Counter from(00 - FFh) of Timer1 */ /*  If it's failed it is raptor 16 phase 1 thatdoes not support watchdog */ #define WS_SYS_TEMP_DATA 0x02030300 /* (S)Temperatures of all sensors on temperature bus in address order */#define WS_SB_FAN_HI 0x03010100 /* (L) System Board Fans HI */ #defineWS_SB_FAN_LED 0x03010200 /* (L) System Board Fan Fault LED */ #defineWS_SYS_RUN 0x03010300 /* (L) Controls the system halt/run lineS1_OK_TO_RUN. */ #define WS_SYS_SB_TYPE 0x03010400 /* (L) Set SystemType (0: Raptor16 or 1:Raptor 8) */ #define WS_SB_BUSCORE 0x03020200 /*(B) System Board BUS/CORE speed ratio to use on reset */ #defineWS_SB_FANFAULT 0x03020300 /* (B) System Board Fan fault bits */ #defineWS_SB_FAN_LOLIM 0x03020400 /* (B) Fan speed low speed fault limit */#define WS_SB_LCD_COMMAND 0x03020500 /* (B) Low level LCD ControllerCommand */ #define WS_SB_LCD_DATA 0x03020600 /* (B) Low level LCDController Data */ #define WS_LCD_MSG 0x03020700 /* (B) Send a Byte ofFault Bits from Monitor-B to Monitor-A */ #define WS_SB_DIMM_TYPE0x03030300 /* (S) The type of DIMM in each DIMM socket as a 16 bytestring */ #define WS_SB_FAN_DATA 0x03030400 /* (S) System Board Fanspeed data in fan number order */ #define WS_SYS_LCD1 0x03030500 /* (S)Value to display on LCD Top line */ #define WS_SYS_LCD2 0x03030600 /*(S) Value to display on LCD Bottom line */ #define WS_SB_LCD_STRING0x03030700 /* (S) Low Level LCD Display string at current position */#define WS_SYS_MESSAGE 0x03030800 /* (S) Value to stored from LCDMessages */ #define WS_NMI_REQ 0x04010100 /* (L) NMI Request bit */#define WS_SB_CPU_FAULT 0x04010200 /* (L) CPU Fault Summary */ #defineWS_SB_FLASH_ENA 0x04010300 /* (L) Indicates FLASH ROW write enabled */#define WS_SB_FRU_FAULT 0x04010400 /* (L) Indicates the FRU status */#define WS_SB_JTAG 0x04010500 /* (L) Enables JTAG chain on system board*/ #define WS_SYSFAULT 0x04010600 /* (L) System Fault Summary */ #defineWS_SYS_OVERTEMP 0x04010700 /* (L) Indicates Overtemp fault */ #defineWS_CAN1_FAN_SYSFLT 0x04010800 /* (L) Indicates Canister #1 Fan SystemFault */ #define WS_CAN2_FAN_SYSFLT 0x04010900 /* (L) Indicates Canister#2 Fan System Fault */ #define WS_CAN3_FAN_SYSFLT 0x04010A00 /* (L)Indicates Canister #3 Fan System Fault */ #define WS_CAN4_FAN_SYSFLT0x04010B00 /* (L) Indicates Canister #4 Fan System Fault */ #defineWS_NMI_MASK 0x04020100 /* (B) CPU NMI processor mask (LSB=CPU1) */#define WS_SB_CPU_ERR 0x04020200 /* (B) CPU Error bits (LSB = CPU1) */#define WS_SB_CPU_POK 0x04020300 /* (B) CPU Power OK (LSB = CPU1) */#define WS_SB_CPU_PRES 0x04020400 /* (B) CPU Presence bits (LSB = CPU1)*/ #define WS_SB_CPU_TEMP 0x04020500 /* (B) CPU Thermal fault bits (LSB= CPU1) */ #define WS_SI_EVENTS 0x10050100 /* (E) System Interface EventQueue */ #define WS_RI_CD 0x11010100 /* (L) Status of Remote Port ModemCD */ #define WS_RI_CTS 0x11010200 /* (L) Status of Remote Port ModemCTS */ #define WS_RI_DSR 0x11010300 /* (L) Status of Remote Port ModemDSR */ #define WS_RI_DTR 0x11010400 /* (L) State of Remote Port ModemDTR */ #define WS_RI_RTS 0x11010500 /* (L) Status of Remote Port ModemRTS */ #define WS_RI_CALLOUT 0x11020100 /* (B) Controls Call out Scriptactivation */ #define WS_CALLOUT_STATUS 0x11020200 /* (B) Read Call OutStatus */ #define WS_RI_EVENTS 0x11050100 /* (E) Remote Interface EventQueue */ #define WS_CAN_FAN_HI 0x20010100 /* (L) Canister Fans HI */#define WS_CAN_FAN_LED 0x20010200 /* (L) Canister Fan Fault LED */#define WS_CAN_POWER 0x20010500 /* (L) Controls canister PCI slot power*/ #define WS_CAN_S5_PRESENT 0x20010600 /* (L) Indicates the presence ofsomething in slot 5 */ #define WS_SYS_CAN_TYPE 0x20010700 /* (L) SetSystem Type (0: Raptor16 or 1:Raptor 8) */ #define WS_CAN_FAN_LOLIM0x20020100 /* (B) Fan low speed fault limit */ #defineWS_CAN_PCI_PRESENT 0x20020200 /* (B) Reflects PCI card slot[1..4]presence indicator pins ( MSB to LSB) 4B,4A,3B,3A,2B,2A,1B,1A */ #defineWS_CAN_FANFAULT 0x20020300 /* (B) Canister Fan Fault Bits */ #defineWS_PCI_SLOT_PWR 0x20020400 /* (B) Turn on/off PCI Slot of Raptor 8 */#define WS_CAN_FAN_DATA 0x20030300 /* (S) Canister Fan speed data */ /********************************************************** */ /*  This isthe Wire Service Attributes for named items. */ /*  The attributeinformation is stored in a symbolic constant named the same */ /*  asthe named item then followed by two underscores */ /*  */ /*  Attributesconsist of: */ /*    R/W access for internal WS (I), BIOS/OS (O),administrator (A), and general (G) */ /*    groups. (0 = NoAccess 1 =Read Only, 2 = Write Only, 3 = Read/Write) */ /*  */ /*    maximumpossible request/response length of item in bytes (LL) */ /*  */ /*   Group Name ID (ID) */ /*  */ /* IOAGLLID */ #defineWS_DESCRIPTION_(—) 0x11114000 /* (S) Wire Service ProcessorType/Description */ #define WS_REVISION_(—) 0x11112000 /* (S) WireService Software Revision/Date Info */ #define WS_WDOG_CALLOUT_(—)0x33310100 /* (L) This is a bit controlling callout on a watchdogtimeout. */ #define WS_WDOG_RESET_(—) 0x33310100 /* (L) This is a bitcontrolling system on a watchdog timeout. */ #define WS_NVRAM_RESET_(—)0x22200100 /* (B) Trigger to reset NVRAM Data */ #defineWS_SYS_BOOTFLAG1_(—) 0x33310100 /* (B) System Boot Flag 1 */ #defineWS_SYS_BOOTFLAG2_(—) 0x33310100 /* (B) System Boot Flag 2 */ #defineWS_SYS_BOOTFLAG3_(—) 0x33310100 /* (B) System Boot Flag 3 */ #defineWS_SYS_BOOTFLAG4_(—) 0x33310100 /* (B) System Boot Flag 4 */ #defineWS_SYS_XDATA_KBYTES_(—) 0x11110100 /* (B) Size of the WS_SYS_XDATA inkilobytes */ #define WS_SYS_XDATA_(—) 0x3331ff00 /* Byte Array forstorage of arbitrary external data in NVRAM */ #defineWS_NVRAM_FAULTS_(—) 0x11110100 /* (B) Faults detected in NVRAM Data */#define WS_SYS_LOG_(—) 0x3311ff00 /* System Log */ #defineWS_RI_QUEUE_(—) 0x3300ff00 /* (Q) Queue of data going to RemoteInterface */ #define WS_SI_QUEUE_(—) 0x3300ff00 /* (Q) Queue of datagoing to System Interface */ #define WS_SYS_SCREEN_(—) 0x3311ff00 /*System Screen */ #define WS_CALLOUT_SCRIPT_(—)  0x3330ff00 /* (S) Thecallout script for remote notification */ #define WS_PASSWORD_(—)0x33301000 /* (S) The access password for Wire Service */ #defineWS_SYS_BP_SERIAL_(—) 0x31111000 /* (S) Last known Back Plane serial data*/ #define WS_SYS_CAN_SERIAL1_(—)  0x31111000 /* (S) Last known Canister1 Serial data */ #define WS_SYS_CAN_SERIAL2_(—)  0x31111000 /* (S) Lastknown Canister 2 Serial data */ #define WS_SYS_CAN_SERIAL3_(—) 0x31111000 /* (S) Last known Canister 3 Serial data */ #defineWS_SYS_CAN_SERIAL4_(—)  0x31111000 /* (S) Last known Canister 4 Serialdata */ #define WS_SYS_RI_SERIAL_(—) 0x31111000 /* (S) Last known RemoteInterface serial data */ #define WS_SYS_SB_SERIAL_(—) 0x31111000 /* (S)Last known System Board serial data */ #define WS_SYS_PS_SERIAL1_(—)0x31111000 /* (S) Last known Power Supply 1 serial data */ #defineWS_SYS_PS_SERIAL2_(—) 0x31111000 /* (S) Last known Power Supply 2 serialdata */ #define WS_SYS_PS_SERIAL3_(—) 0x31111000 /* (S) Last known PowerSupply 3 serial data */ #define WS_NAME_(—) 0x33312000 /* (S) SystemIdentifying Name */ #define WS_BOOTDEVS_(—) 0x3331ff00 /* (S) BIOS Bootdrive information */ #define WS_SYS_LOG_CLOCK_(—) 0x11110400 /* (S)Current time from log timestamp clock (seconds) */ #defineWS_SYS_LOG_COUNT_(—) 0x11110200 /* (S) Number of Log entries */ #defineWS_MODEM_INIT_(—) 0x33315000 /* (S) Modem initialization string */#define WS_EVENT_ID01_(—) 0x31111000 /* (S) Canister Change Event */#define WS_EVENT_ID02_(—) 0x31111000 /* (S) Power Supply Change Event */#define WS_EVENT_ID03_(—) 0x31111000 /* (S) Queue Event */ #defineWS_EVENT_ID04_(—) 0x31111000 /* (S) Temp Warn or Shut Event */ #defineWS_EVENT_ID05_(—) 0x31111000 /* (S) ACOK Change Event */ #defineWS_EVENT_ID06_(—) 0x31111000 /* (S) DCOK Change Event */ #defineWS_EVENT_ID07_(—) 0x31111000 /* (S) Fan Fault Event */ #defineWS_EVENT_ID08_(—) 0x31111000 /* (S) Screen Event */ #defineWS_EVENT_ID09_(—) 0x31111000 /* (S) CPU Fault Event */ #defineWS_EVENT_ID0A_(—) 0x31111000 /* (S) OS_TimeOut Event */ #defineWS_CALLOUT_MASK_(—) 0x31110200 /* (S) Call Out Masking string */ #defineWS_BIOS_REV_(—) 0x31111000 /* (S) Storage of current BIOS Revision */#define WS_SYS_POWER_(—) 0x33310100 /* (L) Controls system master powerS4_POWER_ON */ #define WS_SYS_REQ_POWER_(—) 0x22200100 /* (L) Set torequest main power on */ #define WS_BP_P12V_(—) 0x11110100 /* (B) AnalogMeasure of +12 volt main supply */ #define WS_BP_P3V_(—) 0x11110100 /*(B) Analog Measure of +3.3 volt main supply */ #define WS_BP_N12V_(—)0x11110100 /* (B) Analog Measure of −12 volt main supply */ #defineWS_BP_P5V_(—) 0x11110100 /* (B) Analog Measure of +5 volt main supply */#define WS_BP_VREF_(—) 0x11110100 /* (B) Analog Measure of VREF */#define WS_SYS_BP_TYPE_(—) 0x11110100 /* (B) Type of system backplanecurrently only two types Type 0= 4 canister (small) and Type 1= 8canister (large) */ #define WS_SYS_CAN_PRES_(—) 0x11110100 /* (B)Presence bits for canisters (LSB=1, MSB=8) */ #define WS_SYS_PS_ACOK_(—)0x11110100 /* (B) Power supply ACOK status (LSB=1, MSB=3) */ #defineWS_SYS_PS_DCOK_(—) 0x11110100 /* (B) Power supply DCOK status (LSB=1,MSB=3) */ #define WS_SYS_PS_PRES_(—) 0x11110100 /* (B) Presence bits forpower supplies (LSB=1, MSB=3) */ #define WS_SYS_RSTIMER_(—) 0x33310100/* (B) Used to delay reset/run until power stabilized */ #defineWS_SYS_TEMP_SHUT_(—) 0x33310100 /* (B) Shutdown temperature. Initializedto ??? */ #define WS_SYS_TEMP_WARN_(—) 0x33310100 /* (B) Warningtemperature. Initialized to ??? */ #define WS_SYS_WDOG_(—) 0x33110100 /*(B) System watchdog timer */ /*  First issues following command in phase2 */ #define WS_OS_RESOLUTION_16_(—) 0x33110100 /* (B) Set Resolution(0,1,2,3) of Timer1 */ #define WS_OS_COUNTER_16_(—) 0x33110100 /* (B)Set Counter from (00 - FFh) of Timer1 */ /*  If either operation'sfailed that it will response error code “02h” back, then try raptor 8and future command */ #define WS_OS_RESOLUTION_8_(—) 0x33110100 /* (B)Set Resolution (0,1,2,3) of Timer1 */ #define WS_OS_COUNTER_8_(—)0x33110100 /* (B) Set Counter from (00 - FFh) of Timer1 */ /*  If it'sfailed it is raptor 16 phase 1 that does not support watchdog */ #defineWS_SYS_TEMP_DATA_(—) 0x11110500 /* (S) Temperatures of all sensors ontemperature bus in address order */ #define WS_SB_FAN_HI_(—) 0x33310100/* (L) System Board Fans HI */ #define WS_SB_FAN_LED_(—) 0x33110100 /*(L) System Board Fan Fault LED */ #define WS_SYS_RUN_(—) 0x33310100 /*(L) Controls the system halt/run line S1_OK_TO_RUN. */ #defineWS_SYS_SB_TYPE_(—) 0x33310100 /* (L) Set System Type (0:Raptor 16 or1:Raptor 8) */ #define WS_SB_BUSCORE_(—) 0x33110100 /* (B) System BoardBUS/CORE speed ratio to use on reset */ #define WS_SB_FANFAULT_(—)0x33110100 /* (B) System Board Fan fault bits */ #defineWS_SB_FAN_LOLIM_(—) 0x33310100 /* (B) Fan speed low speed fault limit */#define WS_SB_LCD_COMMAND_(—)  0x22000100 /* (B) Low level LCDController Command */ #define WS_SB_LCD_DATA_(—) 0x22000100 /* (B) Lowlevel LCD Controller Data */ #define WS_LCD_MSG_(—) 0x33110100 /* (B)Send a Byte of Fault Bits from Monitor-B to Monitor-A */ #defineWS_SB_DIMM_TYPE_(—) 0x11111000 /* (S) The type of DIMM in each DIMMsocket as a 16 byte string */ #define WS_SB_FAN_DATA_(—) 0x11110600 /*(S) System Board Fan speed data in fan number order */ #defineWS_SYS_LCD1_(—) 0x33311000 /* (S) Value to display on LCD Top line */#define WS_SYS_LCD2_(—) 0x33311000 /* (S) Value to display on LCD Bottomline */ #define WS_SB_LCD_STRING_(—) 0x22004000 /* (S) Low Level LCDDisplay string at current position */ #define WS_SYS_MESSAGE_(—)0x11112000 /* (S) Value to stored from LCD Messages */ #defineWS_NMI_REQ_(—) 0x22200100 /* (L) NMI Request bit */ #defineWS_SB_CPU_FAULT_(—) 0x11110100 /* (L) CPU Fault Summary */ #defineWS_SB_FLASH_ENA_(—) 0x33310100 /* (L) Indicates FLASH ROW write enabled*/ #define WS_SB_FRU_FAULT_(—) 0x33110100 /* (L) Indicates the FRUstatus */ #define WS_SB_JTAG_(—) 0x33310100 /* (L) Enables JTAG chain onsystem board */ #define WS_SYSFAULT_(—) 0x33110100 /* (L) System FaultSummary */ #define WS_SYS_OVERTEMP_(—) 0x11110100 /* (L) IndicatesOvertemp fault */ #define WS_CAN1_FAN_SYSFLT_(—)  0x33110100 /* (L)Indicates Canister #1 Fan System Fault */ #define WS_CAN2_FAN_SYSFLT_(—) 0x33110100 /* (L) Indicates Canister #2 Fan System Fault */ #defineWS_CAN3_FAN_SYSFLT_(—)  0x33110100 /* (L) Indicates Canister #3 FanSystem Fault */ #define WS_CAN4_FAN_SYSFLT_(—)  0x33110100 /* (L)Indicates Canister #4 Fan System Fault */ #define WS_NMI_MASK_(—)0x33310100 /* (B) CPU NMI processor mask (LSB=CPU1) */ #defineWS_SB_CPU_ERR_(—) 0x11110100 /* (B) CPU Error bits (LSB = CPU1) */#define WS_SB_CPU_POK_(—) 0x11110100 /* (B) CPU Power OK (LSB = CPU1) */#define WS_SB_CPU_PRES_(—) 0x11110100 /* (B) CPU Presence bits (LSB =CPU1) */ #define WS_SB_CPU_TEMP_(—) 0x11110100 /* (B) CPU Thermal faultbits (LSB = CPU1) */ #define WS_SI_EVENTS_(—) 0x33001000 /* (E) SystemInterface Event Queue */ #define WS_RI_CD_(—) 0x33110100 /* (L) Statusof Remote Port Modem CD */ #define WS_RI_CTS_(—) 0x33110100 /* (L)Status of Remote Port Modem CTS */ #define WS_RI_DSR_(—) 0x33110100 /*(L) Status of Remote Port Modem DSR */ #define WS_RI_DTR_(—) 0x33110100/* (L) State of Remote Port Modem DTR */ #define WS_RI_RTS_(—)0x33110100 /* (L) Status of Remote Port Modem RTS */ #defineWS_RI_CALLOUT_(—) 0x33310100 /* (B) Controls Call out Script activation*/ #define WS_CALLOUT_STATUS_(—)  0x33310100 /* (B) Read Call Out Status*/ #define WS_RI_EVENTS_(—) 0x33002000 /* (E) Remote Interface EventQueue */ #define WS_CAN_FAN_HI_(—) 0x33310100 /* (L) Canister Fans HI */#define WS_CAN_FAN_LED_(—) 0x33310100 /* (L) Canister Fan Fault LED */#define WS_CAN_POWER_(—) 0x33310100 /* (L) Controls canister PCI slotpower */ #define WS_CAN_S5_PRESENT_(—)  0x11110100 /* (L) Indicates thepresence of something in slot 5 */ #define WS_SYS_CAN_TYPE_(—)0x33310100 /* (L) Set System Type (0: Raptor 16 or 1: Raptor 8) */#define WS_CAN_FAN_LOLIM_(—) 0x33310100 /* (B) Fan low speed fault limit*/ #define WS_CAN_PCI_PRESENT_(—)  0x11110100 /* (B) Reflects PCI cardslot[1..4] presence indicator pins ( MSB to LSB) 4B,4A,3B,3A,2B,2A,1B,1A*/ #define WS_CAN_FANFAULT_(—) 0x11110100 /* (B) Canister Fan Fault Bits*/ #define WS_PCI_SLOT_PWR_(—) 0x33310100 /* (B) Turn on/off PCI Slot ofRaptor 8 */ #define WS_CAN_FAN_DATA_(—) 0x11110200 /* (S) Canister Fanspeed data */ #ifndef FAR_POINTERS #ifndef NEAR_POINTERS #include“***ERROR - Pointer Type not defined” #endif #endif

What is claimed is:
 1. A computer comprising: a central processing unit;a fan; and a network of microcontrollers comprising: a system recordermicrocontroller configured to record system and error messages; a systeminterface microcontroller in communication with the central processingunit, the system interface microcontroller configured to send andreceive messages to and from the central processing unit, wherein atleast one message requests information about the fan in the computer;and at least one microcontroller configured to adjust the speed of thefan in the computer.
 2. The computer of claim 1, wherein themicrocontrollers belonging to the network of microcontrollers areinterconnected by a microcontroller bus.
 3. The computer of claim 1,wherein the system recorder microcontroller is configured to maintain asystem log in a non-volatile memory.
 4. The computer of claim 1, whereinadjusting the speed of the fan in the computer comprises adjusting thespeed of a canister fan.
 5. The computer of claim 1, wherein the networkof microcontrollers further comprises at least one microcontrollerconfigured to monitor the speed of a canister fan.
 6. The computer ofclaim 1, wherein the network of microcontrollers further comprises atleast one microcontroller configured to monitor the speed of a chassisfan.
 7. The computer of claim 1, wherein the network of microcontrollersfurther comprises at least one microcontroller configured to monitor thespeed of a PCI card fan.
 8. The computer of claim 1, wherein the networkof microcontrollers further comprises at least one microcontrollerconfigured to monitor the speed of a backplane fan.
 9. The computer ofclaim 1, wherein the network of microcontrollers further comprises atleast one microcontroller configured to control system power to thecomputer.
 10. The computer of claim 1, wherein the computer furthercomprises a plurality of canisters, and wherein the network ofmicrocontrollers further comprises a microcontroller configured tocontrol power to the plurality of canisters.
 11. The computer of claim1, wherein the network of microcontrollers further comprises at leastone microcontroller connected to a canister.
 12. The computer of claim1, wherein one of the microcontrollers transmits the information to thesystem interface microcontroller in real time.
 13. The computer of claim1, wherein a remote computer requests a change in a selected one of aplurality of environmental conditions, at least one of the plurality ofenvironmental conditions controlled by at least one of themicrocontrollers belonging to the network of microcontrollers.
 14. Thecomputer of claim 1, wherein the network of microcontrollers comprises amicrocontroller configured to detect the temperature in the computer.15. The computer of claim 1, wherein a remote computer requests a changein the fan speed.
 16. The computer of claim 1, wherein a remote computerrequests a change in power to a canister.
 17. The computer of claim 14,wherein at least one of the network of microcontrollers is configured toadjust the speed of a chassis fan.
 18. The computer of claim 14, whereinat least one of the network of microcontrollers is configured to adjustthe speed of a PCI card fan.
 19. The computer of claim 14, wherein atleast one of the network of microcontrollers is configured to adjustspeed of a backplane fan.
 20. A computer comprising: a centralprocessing unit; a network interface port; a fan; and a network ofmicrocontrollers, wherein said network of microcontrollers areconfigured to: monitor the environmental condition of one or morecomponents within the computer; record a system error message, includingthe generation of the system error message upon detecting that anenvironmental condition is not within an acceptable range; and send andreceive messages to and from the central processing unit.
 21. Thecomputer of claim 20, wherein the computer is configured to receive arequest from a remote computer via the network interface port to changea threshold for the environmental condition; and wherein said network ofmicrocontrollers is configured to change the threshold for theenvironmental condition in response to said received request.
 22. Thecomputer of claim 20, wherein the environmental condition comprises atemperature condition within the computer.
 23. The computer of claim 20,wherein the network of microcontrollers is further configured to controlsystem power for the computer.
 24. The computer of claim 20, wherein thenetwork of microcontrollers is further configured to monitor the speedof the fan.
 25. The computer of claim 20, wherein the computer furthercomprises a hardware sub-component, and wherein the network ofmicrocontrollers is further configured to control power to the hardwaresub-component.
 26. The computer of claim 20, wherein the network ofmicrocontrollers is configured to adjust the speed of the fan in thecomputer in response to the detected environmental condition. 27.Computerized apparatus, comprising: a central processing unit; a networkinterface port; an environmental sensing apparatus; an environmentalcontrol apparatus; and a plurality of microcontrollers, wherein saidplurality of microcontrollers are configured to: monitor theenvironmental condition of one or more components via said environmentalsensing apparatus; record a system error condition based on thegeneration of a system error message upon detecting that anenvironmental condition is not at an acceptable value; and send andreceive messages to and from the central processing unit.
 28. Thecomputerized apparatus of claim 27, wherein the computerized apparatusis configured to receive a request from a remote computer via thenetwork interface port to change a threshold for the environmentalcondition; and wherein said network of microcontrollers is configured tochange the threshold for the environmental condition in response to saidreceived request.
 29. The computerized apparatus of claim 27, whereinthe environmental condition comprises a temperature condition within acomputer.
 30. The computerized apparatus of claim 29, wherein thecomputer comprises the computerized apparatus.
 31. The computerizedapparatus of claim 27, wherein the plurality of microcontrollerscomprises a network of microcontrollers further configured to control atleast one operational parameter of the environmental control apparatus.32. The computerized apparatus of claim 31, wherein the at least oneoperational parameter comprises the speed of a cooling fan.